Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/agentrust-io/integrations/manifestgit clone --depth 1 https://github.com/agentrust-io/integrationsWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00014 | $0.00514 |
| Opus 5 | $0.00007 | $0.00257 |
| Sonnet 5 | $0.00003 | $0.00103 |
| Haiku 4.5 | $0.00001 | $0.00051 |
Grade A, and why
manifest scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
You are running the AgenTrust agent-integrity command. It answers one question for the user: is the agent they are running the one they approved, with nothing added and nothing subtracted since their baseline?
The engine is at ${CLAUDE_PLUGIN_ROOT}/engine/capture.py. It captures the
agent's composition (skills, tools, MCP servers, model, permissions, instruction
layer) and diffs it against the approved baseline at
~/.claude/agentrust/baseline.json.
The shell hook cannot see the live tool roster, so YOU enrich it. Before running,
write the current session's real facts to a temp live.json. Use real values you
actually observe this session, never invented ones:
{
"model_id": "<the model you are running>",
"model_provider": "anthropic",
"model_version": "<version>",
"builtin_tools": ["<your actual built-in tool names>"],
"mcp_servers": ["<the MCP servers actually connected this session>"]
}
Then dispatch on $ARGUMENTS:
verify(default): runpython "${CLAUDE_PLUGIN_ROOT}/engine/capture.py" verify --live-context live.json. Verify always re-reads the setup fresh and merges yourlive.json, so it reflects the agent's state right now, including drift introduced partway through this session. Show the result and explain any change in plain language, then ask whether to approve it.approve: runpython "${CLAUDE_PLUGIN_ROOT}/engine/capture.py" approve --live-context live.json --sign --out .to make the current composition the new approved baseline and write signed records. Use this when the user confirms the changes are intentional.show: runpython "${CLAUDE_PLUGIN_ROOT}/engine/capture.py" snapshot --live-context live.jsonto display the current composition without touching the baseline.
Report the result in plain English. Name the categories that changed (a skill, a permission, an MCP server, the instruction layer) and what the user should do about each. Never claim hardware attestation: on a normal dev box this is software-only (Level 0) integrity, not silicon-rooted proof.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 49 lines · 14 tokens per session scan A eee12f2c0032
manifest is a command published in the GitHub repository agentrust-io/integrations (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 14 tokens to every session and 514 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.