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/chris-dare-dev/agent-kitWrote 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/chris-dare-dev/agent-kit/spike)<a href="https://agentmods.dev/commands/chris-dare-dev/agent-kit/spike"><img src="https://agentmods.dev/badge/commands/chris-dare-dev/agent-kit/spike/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/chris-dare-dev/agent-kit/spike"><img src="https://agentmods.dev/badge/commands/chris-dare-dev/agent-kit/spike.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.00136 | $0.04925 |
| Opus 5.5 | $0.00054 | $0.01970 |
| Sonnet 5.5 | $0.00027 | $0.00985 |
| Haiku 4.5 | $0.00014 | $0.00492 |
Grade A, and why
spike 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 1mo 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 — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spike Pipeline Orchestrator
A spike answers exactly one assumption with measured data. POC code is throwaway; the durable artifacts are note.md and review.md. In spike v2 the run is governed by a machine state file (state.json, owned by spike-checkpoint.py) — every phase transition is evidence-gated, the verdict is derived (spike-decide.py), and completion is never inferred from which files happen to exist. Read data/references/spike-protocol.md, spike-state-schema.md, spike-artifact-schema.md, and spike-agent-contract.md.
Arguments: $ARGUMENTS — parse as <spike-id> [--resume] [--executor deep] [--skip-review]
<spike-id>— required. Everything before the first--. Shape:^[a-z][a-z0-9-]*-spike-[0-9]+$(validated in Step 0). The id is<topic>-spike-<N>.--resume— readstate.json; continue from the phase it records. (Resume is state-driven regardless of this flag; it just skips the "fresh vs resume" prompt.)--executor deep— run the executor at policy classdeep-reasoning-high(dispatch model override — pass only the model token: fable (effort: high)) instead of its default classbalanced-high. Roughly doubles cost. Legacy spelling--executor opusis accepted.--skip-review— stop after Phase 3 (note.md); record the auditedskip-reviewterminal (which still requires a canonical derived verdict). Use only for quick internal spikes.
If $ARGUMENTS is empty or has no spike-id, STOP and ask: "What is the spike id? (e.g., kiali-multicluster-spike-1)".
When to use / When NOT to use
Use /spike |
Use /milestone-pipeline |
Use neither |
|---|---|---|
| Answering ONE binary/three-way assumption | Shipping code that implements a feature | Exploration without a specific question |
| Validating a design decision before committing | Full research → implement → critique → rectify | Refactors, lint, doc-only changes |
| Time-boxed, throwaway POC | Durable, reviewed, committed code | Single-file fixes (use Edit directly) |
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.
- 1mo ago First seen · 352 lines · 136 tokens per session scan A 91ac118a85ce
spike is a command published in the GitHub repository chris-dare-dev/agent-kit (0 stars, last pushed 2mo ago), licensed MIT. It adds 136 tokens to every session and 4,925 once invoked, about $0.0005 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-08-31.
Other commands, from other repositories
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.