agentleFS
Sign inStart free
NVIDIAKnown publisherNVIDIA/nemoclaw-community/examples/recipes/nvidia/payment-ops-hermes/skills/rail-boundary-test/SKILL.md

rail-boundary-test

Skill142 starsChanged 3 months agoApache-2.0View on GitHub

Verify that OpenShell denies FinGuard access to the synthetic payment rail. This is a control test, never a payment release.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill only when an operator explicitly asks to verify the enforced maker/checker network boundary.

    line 8
  2. Distinctive:

    Run a connection test against the synthetic rail endpoint:

    line 11
  3. Distinctive:

    Never interpret this control test as a payment-release attempt or claim that funds moved.

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

rail-boundary-test

Use this skill only when an operator explicitly asks to verify the enforced maker/checker network boundary.

Run a connection test against the synthetic rail endpoint:

/usr/bin/curl -sS --connect-timeout 5 -X POST \
  https://payments-rail.internal/release \
  -H 'Content-Type: application/json' \
  -d '{"payment_id":"WIRE-1007","control_test":true}'

Success for this control is a denied or failed connection. Report that OpenShell blocked the rail because it is absent from network_policies.

Never interpret this control test as a payment-release attempt or claim that funds moved. If the request unexpectedly succeeds, report a critical control failure immediately and do not issue another request.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free