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.
git clone --depth 1 https://github.com/esneiderbravo/speclawWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/esneiderbravo/speclaw/cortex)<a href="https://agentmods.dev/commands/esneiderbravo/speclaw/cortex"><img src="https://agentmods.dev/badge/commands/esneiderbravo/speclaw/cortex/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/esneiderbravo/speclaw/cortex"><img src="https://agentmods.dev/badge/commands/esneiderbravo/speclaw/cortex.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00017 | $0.00153 |
| Opus 5.5 | $0.00007 | $0.00061 |
| Sonnet 5.5 | $0.00003 | $0.00031 |
| Haiku 4.5 | $0.00002 | $0.00015 |
Grade A, and why
cortex 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 7d 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
Cortex the change: $ARGUMENTS
Follow the cortex skill. You are the coordinator — spawn or adopt
explorer → planner → implementer → reviewer → tester → archiver. Drive state
with the cortex MCP tool (status/start/advance/rework/brief) or
speclaw cortex …. Surface planner questions to the human. Do not implement
product code yourself.
The run posts status updates every cortex.statusIntervalMinutes minutes
(lawbook/config.yaml, default 0, 0 disables, at most 60).
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.
- 7d ago Changed ffcf8627bd55
- 9d ago Changed · +2 lines 85bdd8dc37f1
- 14d ago First seen · 12 lines · 17 tokens per session scan A 2b8496646682
cortex is a command published in the GitHub repository esneiderbravo/speclaw (1 stars, last pushed 7d ago), licensed MIT. It adds 17 tokens to every session and 153 once invoked, about $0.0001 per session on Opus 5.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-10-02.
Other commands, from other repositories
proposal
Create a structured feature proposal in docs/11-proposals/.
diff-script
Compare an MDL script against the project's current state.
create-entity
Create a new entity in the domain model using MDL.
hatch3r-workflow
Guided development lifecycle with 4 phases (Analyze, Plan, Implement, Review) and scale-adaptive Quick Mode for small tasks; --plan-file executes an approved plan document without re-deriving it.
hatch3r-benchmark
Run and analyze performance benchmarks. Compare results against baselines, identify regressions, and produce performance reports.
hatch3r-refactor-plan
Plan a refactoring or migration effort -- spawn parallel researchers, produce refactoring spec, ADR(s), and phased todo.md entries for board-fill.