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/buildgit 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.00014 | $0.01947 |
| Opus 5 | $0.00007 | $0.00974 |
| Sonnet 5 | $0.00003 | $0.00389 |
| Haiku 4.5 | $0.00001 | $0.00195 |
Grade C, and why
build scanned grade C 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .haytham/session/ How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Haytham: Build Setup (Phase 5 - BUILD)
You are setting up a new project directory from Haytham's Phase 4 OpenSpec output. Implementation happens in a SEPARATE Claude Code session to ensure the code is generated purely from specs, not from the current plugin context.
Prerequisites
Verify .haytham/session/phase-4-specs/openspec/config.yaml exists. If it doesn't, tell the user:
"Phase 4 (specification) must be completed first. Run
/haytham:planto start."
Check that the user provided a project directory argument. If not, read .haytham/session/phase-4-specs/openspec/config.yaml, extract the name field, and use it as the directory name.
Verify the OpenSpec CLI is installed:
command -v openspec
If not found, tell the user to install it with npm install -g @fission-ai/openspec@latest and re-run /haytham:build. Stop here.
Build
-
Check if the project directory already exists. If it does, ask the user if they want to overwrite.
-
Create the directory and initialize OpenSpec:
mkdir -p <project-directory> && cd <project-directory> && openspec init --tools claude -
Copy project context files:
- Copy
.haytham/session/phase-4-specs/openspec/project.mdto<project-directory>/openspec/project.md, overwriting the default. - Copy
.haytham/session/phase-4-specs/openspec/config.yamlto<project-directory>/openspec/config.yaml. This carries project metadata (name, description, tech choices) that downstream tools need.
- Copy
-
Copy domain specs: copy all spec directories from
.haytham/session/phase-4-specs/openspec/specs/into<project-directory>/openspec/specs/. Preserve the directory structure (each{domain}/spec.md). -
Create the
initial-mvpchange directory and seed it:mkdir -p <project-directory>/openspec/changes/initial-mvp cp -r <project-directory>/openspec/specs <project-directory>/openspec/changes/initial-mvp/specsThen read
.haytham/session/phase-3-how/research-directives.jsonand generate<project-directory>/openspec/changes/initial-mvp/design.mdcontaining the resolved research findings for capabilities that haveresearch_required: true. Format as a markdown document with one section per capability. For each capability, list the research findings (verified integration patterns, env var names, SDK methods, API details) as actionable implementation guidance. If a directive has bothquestionsandfindings, present the findings as resolved answers. If a directive has questions but no findings, flag them explicitly as unresolved and mark them as requiring resolution during implementation: "⚠️ UNRESOLVED: [question]. This must be resolved during implementation. Do not proceed with assumptions." The coding agent must resolve these before implementing the affected capability.
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 · 136 lines · 14 tokens per session scan C f5ba3e17c726
build is a command published in the GitHub repository arslan70/haytham (13 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 1,947 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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.
constitution
Create or update the project constitution from interactive or provided principle inputs.