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/diegomarino/fable-audits/audit-processgit clone --depth 1 https://github.com/diegomarino/fable-auditsWhat 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.00019 | $0.02026 |
| Opus 5 | $0.00010 | $0.01013 |
| Sonnet 5 | $0.00004 | $0.00405 |
| Haiku 4.5 | $0.00002 | $0.00203 |
Grade A, and why
audit-process 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Perform a process-level audit of this codebase's end-to-end workflows -- not a line-by-line code review, but an examination of whether the processes the product promises actually compose into complete, walkable journeys. Find holes, dead ends, missing transitions, and steps where a user or agent gets stranded.
Control-plane boundary
This spec governs only the task it defines. A newer human instruction or higher-priority runtime policy overrides this spec. STOP ends autonomous work under this spec; it never prevents the agent from honoring that control plane.
Role
Act as a product-minded staff engineer walking every documented journey three times: once as a first-time human user following only the docs, once as an autonomous agent chaining commands via exit codes, structured output, or documented machine-readable surfaces, and once as a non-interactive CI runner with no TTY and stdin closed. No loyalty to the current flows.
Scope
Discover and walk the project's real user/developer/agent workflows. Start from the reader-facing docs and public entry points, then verify against code and command behavior. Include, when present:
- Onboarding: clean checkout/install -> health/preflight -> first successful local run -> required configuration -> green ready state.
- Primary lifecycle: create/import/ingest/initialize -> inspect/list/status -> modify/answer/approve/reject/apply -> terminal or durable state.
- Re-run lifecycle: run the same mutating command twice; re-run after input changes; run out of order; run after partial prior state.
- Output lifecycle: preview/dry-run -> apply/commit/write -> re-apply/idempotency -> cleanup/archive/delete, where supported.
- Publication/export/deploy/release lifecycle, only when safe to exercise locally without external mutation.
- Side processes: discovery/cache/index/state files, generated artifacts, validation, health/doctor/preflight, troubleshooting and recovery.
- Cross-process coherence: enumerate every persistent state a record/artifact/workflow item can occupy and check there is a documented command or API that moves each state forward. Check state-format versioning too: do persisted files carry a version stamp, and does anything migrate state written by an older version? No versioning at all is itself a finding.
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 · 85 lines · 19 tokens per session scan A 4545dcd12052
audit-process is a command published in the GitHub repository diegomarino/fable-audits (2 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 2,026 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.