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/infinri/writ/writ-approvegit clone --depth 1 https://github.com/infinri/WritWhat 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.00043 | $0.01066 |
| Opus 5 | $0.00022 | $0.00533 |
| Sonnet 5 | $0.00009 | $0.00213 |
| Haiku 4.5 | $0.00004 | $0.00107 |
Grade A, and why
writ-approve scanned grade A 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sX POST http://localhost:8765/session/$SESSION_ID/advance-phase \ How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You have been invoked to advance the Writ workflow phase. Confirm the user's intent is to advance, then run this command via Bash.
Authorization: read this before assuming this command is the primary path
This command does NOT detect approval, and it cannot substitute for detection. Step 3
below reads the gate token, and the ONLY thing that writes that token is
auto-approve-gate.sh when the user's own prompt classified as an exact approval. So on
a detection miss there is no token, this command has nothing to send, and the advance
fails closed. The description used to claim this command replaced pattern matching, which
was never true of its own procedure.
The detector has three tiers (bin/lib/approval_match.py):
- exact: the prompt is an approval. The hook mints a bound token and advances the pending gate itself, so this command is usually unnecessary on that turn.
- embedded: a strong approval word inside a longer sentence, for example "ok remember we want to fix all our findings, approved". Nothing is minted and nothing is advanced. The hook emits a directive naming the pending gate and asks you to confirm the user's intent. ASK; do not call this command to work around it. If the user confirms with "approved", that turn is an exact approval and the hook advances the gate.
- none: not approval-related. Nothing happens.
Procedure
- Check the current phase via
GET /session/$SESSION_ID/current-phase. The response also reportsnext_gate(the gate a token would be bound to) andplan_hash. - If the current phase artifact exists and was presented to the user in this or a prior turn (plan.md for planning, test skeletons for testing, etc.), proceed. Otherwise, respond: "No current phase artifact to approve. Present the artifact first."
- Advance via POST, passing the gate token and the working directory. The token at
/tmp/writ-gate-token-$SESSION_IDis written by the approval hook ONLY when the user's prompt matched an exact approval pattern, so it proves genuine user approval; the advance route requires it and consumes it (one approval = one advance).
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 · 72 lines · 43 tokens per session scan A 5aa943550d75
writ-approve is a command published in the GitHub repository infinri/Writ (189 stars, last pushed 18d ago), licensed MIT. It adds 43 tokens to every session and 1,066 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
make-agent-ready
Make a provider's API agent-ready — comprehend its OpenAPI/docs with gecko, serve the FULL surface over MCP with a one-click add, emit the discovery breadcrumbs, and leave the provider's own MCP intact. Usage: /make-agent-ready.
setup-x402
Wire x402 pay-per-call onto a provider's already-comprehended API via PayAI — point tools at the provider's OWN x402 endpoint, prove the handshake offline (X402MODE=stub), keep the provider at 100%. Gecko never the rail, no cut. Usage: /setup-x402.
llmwiki-query
Query a configured llmwiki-serve instance directly from a local project.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
add-agent
引导新增一个 Agent 适配器。用法 /add-agent.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.