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/arslan70/haytham/plangit clone --depth 1 https://github.com/arslan70/haythamWhat 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.01301 |
| Opus 5 | $0.00008 | $0.00651 |
| Sonnet 5 | $0.00003 | $0.00260 |
| Haiku 4.5 | $0.00002 | $0.00130 |
Grade A, and why
plan 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 3d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Haytham: Specification Generation (Phase 4 - SPECS)
You are running Phase 4 of the Haytham validation workflow. This phase generates an implementation-ready OpenSpec that a coding agent can use to build the system.
IMPORTANT: Always read agent output from files, not from conversation history.
Progress Tracking
After prerequisites pass, call TodoWrite once with:
- Step 1 — OpenSpec generation
- Step 2 — Review
- Step 3 — Detail review (optional drill-in)
Mark each todo in_progress when its step begins and completed when its output is produced or the founder finishes the review. Step 3 completes immediately if the founder says "looks good" without requesting a drill-in.
Prerequisites
Verify .haytham/session/phase-3-how/gate-decision.json exists. If it doesn't, tell the user:
"Phase 3 (technical design) must be completed first. Run
/haytham:designto start."
Roadmap
Before launching any agents, tell the user:
Phase 4: Specification Generation
This will run 3 steps:
- OpenSpec Generation — produce SHALL requirements with Gherkin scenarios (~2 min)
- Review — you review the specification
- Detail Review — drill into specific domains if needed
Estimated total: ~3 minutes.
Step 1: OpenSpec Generation
Create .haytham/session/phase-4-specs/ directory if it doesn't exist.
Tell the user:
Step 1/3: OpenSpec Generation Turning capabilities and architecture decisions into a complete specification with SHALL requirements and testable scenarios.
Launch a spec-generator agent with this task:
Read capabilities from
.haytham/session/phase-2-what/capabilities.json, MVP scope from.haytham/session/phase-2-what/mvp-scope.md, system traits from.haytham/session/phase-2-what/system-traits.json, architecture decisions from.haytham/session/phase-3-how/architecture-decisions.json, build/buy analysis from.haytham/session/phase-3-how/build-buy.json, and concept anchor from.haytham/session/phase-1-why/concept-anchor.json. Generate the OpenSpec directory tree. Write to.haytham/session/phase-4-specs/openspec/(config.yaml, project.md, and specs/*/spec.md).
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.
- 3d ago First seen · 130 lines · 15 tokens per session scan A 1c68df07a7f0
plan is a command published in the GitHub repository arslan70/haytham (13 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 1,301 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-30.
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.