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/schedule-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.00015 | $0.00525 |
| Opus 5 | $0.00008 | $0.00262 |
| Sonnet 5 | $0.00003 | $0.00105 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade B, and why
schedule-manifest scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- the `hooks` block in `~/.claude/settings.json`: the commands that auto-run on What it actually says
You are running the AgenTrust scheduled-agent integrity command. It answers one question: are the things that run WITHOUT the user watching -- their scheduled routines and the hooks that auto-run on events -- the ones they approved, with nothing added and nothing subtracted since their baseline?
The engine is at ${CLAUDE_PLUGIN_ROOT}/engine/capture.py. It fingerprints:
- routine specs in
~/.claude/agentrust/routines/*.json(override withAGENTRUST_ROUTINES_DIR): each routine's schedule, allowed tools, MCP servers, prompt, and model. - the
hooksblock in~/.claude/settings.json: the commands that auto-run on SessionStart, PreToolUse, and other events.
It diffs the current surface against the approved baseline at
~/.claude/agentrust/scheduled/baseline.json. Everything is read from disk, so
no live session context is needed.
Dispatch on $ARGUMENTS:
verify(default): runpython "${CLAUDE_PLUGIN_ROOT}/engine/capture.py" verify. Verify always re-reads the surface fresh, so it reflects any routine edited or hook widened since session start. Show the result and explain each change in plain language, then ask whether to approve it.approve: runpython "${CLAUDE_PLUGIN_ROOT}/engine/capture.py" approve. Use this when the user confirms the changes are intentional. Add--sign --out .to also write a signed TRACE record (needspip install -r "${CLAUDE_PLUGIN_ROOT}/requirements.txt").show: runpython "${CLAUDE_PLUGIN_ROOT}/engine/capture.py" snapshotto display the current surface without touching the baseline.
Report the result in plain English. Name what changed (a routine added, a tool widened, a schedule moved, a new auto-run hook) and what the user should do about each. Be honest about scope: this baselines the DECLARED routine specs and the on-disk hooks, and detects drift in those declarations. It does not introspect a live cloud routine's runtime behaviour, and on a normal dev box it is software-only (Level 0) integrity, not hardware attestation.
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 · 44 lines · 15 tokens per session scan B 3aab2a4fd3bf
schedule-manifest is a command published in the GitHub repository agentrust-io/integrations (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 15 tokens to every session and 525 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.
constitution
Create or update the project constitution from interactive or provided principle inputs.