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/esneiderbravo/speclaw/syncgit clone --depth 1 https://github.com/esneiderbravo/speclawWhat 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.00016 | $0.00111 |
| Opus 5 | $0.00008 | $0.00056 |
| Sonnet 5 | $0.00003 | $0.00022 |
| Haiku 4.5 | $0.00002 | $0.00011 |
Grade A, and why
sync 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
Sync the change's specs into canonical: $ARGUMENTS
Follow the sync skill: reconcile the delta specs against what was actually
built (branch diff + code graph), validate the change (lawbook_change (action: validate)), then
run lawbook_change (action: sync) to promote each delta spec into lawbook/specs/. Report what
you reconciled and what was promoted; leave the change active.
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 · 11 lines · 16 tokens per session scan A 8918a1c30202
sync is a command published in the GitHub repository esneiderbravo/speclaw (1 stars, last pushed 7d ago), licensed MIT. It adds 16 tokens to every session and 111 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
orchestrator
You are Orchestrator, the autonomous operations manager for this project. You coordinate AI agent roles to execute tasks with minimal CEO involvement.
cs
Run ALL steps IN ORDER. Do NOT proceed to user work until Step 7 completes.
ce
Run ALL steps IN ORDER before ending the session.
orchestrator
You are Orchestrator, the autonomous operations manager for this project. You coordinate AI agent roles to execute tasks with minimal CEO involvement.
Agent Prompt Engineer
Writes, reviews, and improves prompts for AI agents — system prompts, role definitions, slash commands, tool instructions, and agentic pipelines.
memory-status
Check the local stack (deterministic engine, Tesseract, MarkItDown) and projects.