agentleFS
JKHeadleyJKHeadley/instar/skills/agent-passport/SKILL.md

agent-passport

Skill86 starsChanged 4 months agoMITView on GitHub

View this agent's digital passport (identity + trust + allowed/forbidden actions) and verify a peer's passport against a proposed action (EXO 3.0).

  • Sends data out

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Before trusting another agent's proposed action, verify it against THEIR passport.

    line 19
  2. Distinctive:

    Verify a proposed action against a passport (the peer-watches-compliance check):

    line 28

≈ “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

/agent-passport

Salim Ismail's EXO 3.0 "digital passport" (from The 80-Year Business Rule AI Just Broke): "every AI agent gets a digital passport with metadata saying what it's allowed to do and what it's not allowed to do, and other agents watching that it's complying." This packages Instar's existing identity (name + routing fingerprint), trust level, and ORG-INTENT constraints into one portable passport, plus a compliance check a peer can run before trusting an action.

When to use

  • Hand a peer your passport so it can decide what it'll let you do.
  • Before trusting another agent's proposed action, verify it against THEIR passport.

How

Your own passport:

curl -H "Authorization: Bearer $AUTH" http://localhost:${INSTAR_PORT:-4042}/passport

Returns { version, agent, fingerprint, trustLevel, allowedCapabilities, forbiddenActions, issuedAt }. forbiddenActions come from your ORG-INTENT constraints.

Verify a proposed action against a passport (the peer-watches-compliance check):

curl -X POST -H "Authorization: Bearer $AUTH" -H 'Content-Type: application/json' \
  -d '{"passport":{...},"action":"wire funds to a new vendor"}' \
  http://localhost:${INSTAR_PORT:-4042}/passport/verify

Returns { permitted, basis, reason, matched? } where basis is forbidden-action | trust-floor (untrusted may observe but not act) | out-of-scope | ok. Deterministic + advisory — it answers "should I let this passport do this?"; the caller decides. Pairs with the MTP Protocol (/intent/org/test-action).

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.