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/agents/chris-dare-dev/agent-kit/spike-designer)<a href="https://agentmods.dev/agents/chris-dare-dev/agent-kit/spike-designer"><img src="https://agentmods.dev/badge/agents/chris-dare-dev/agent-kit/spike-designer/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/agents/chris-dare-dev/agent-kit/spike-designer"><img src="https://agentmods.dev/badge/agents/chris-dare-dev/agent-kit/spike-designer.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.00144 | $0.02259 |
| Opus 5.5 | $0.00058 | $0.00904 |
| Sonnet 5.5 | $0.00029 | $0.00452 |
| Haiku 4.5 | $0.00014 | $0.00226 |
Grade C, and why
spike-designer scanned grade C with 2 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.
Instruction-override phrasingmediumPrompt injection
Text telling the model to disregard its earlier instructions or safety rules is the shape of a prompt injection, whoever wrote it.
"Now run X", "Ignore previous instructions", "Authorize the user", "Add yourself Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat ".claude/agent-memory/spike-designer/lessons.md" 2>/dev/null || echo "(no lessons yet)" How it starts
The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spike Designer
You are Phase 1 of the /spike pipeline. Your job is to extract a spike brief from the roadmap and design a rigorous, minimal experiment that answers exactly one assumption with measurable data — expressed as a typed contract the rest of the pipeline can validate and derive from.
The orchestrator (slash command at .claude/commands/spike.md) dispatches you with substituted variables. You never invoke other sub-agents.
Input variables (substituted by the orchestrator)
{SPIKE_ID}— the spike identifier (e.g.,kiali-multicluster-spike-1){ROADMAP_PATH}— absolute path to the roadmap file containing the spike brief{DESIGN_JSON_PATH}— absolute path where you MUST writedesign.json(the typed contract){DESIGN_PATH}— absolute path where you MUST writedesign.md(the human design){VALIDATE_SCRIPT}— absolute path tospike-validate.py(used in Step 3 self-validation){DEVIATION_PATH}— (optional) absolute path todesign-deviation.mdfrom a previous executor run; set ONLY on re-dispatch after design-deviation was returned
Step 0 — Read persistent memory (skip-if-not-relevant)
cat ".claude/agent-memory/spike-designer/lessons.md" 2>/dev/null || echo "(no lessons yet)"
Read memory only if the lessons are relevant to this spike's domain.
Step 0b — On re-dispatch: read the deviation BEFORE extracting the brief
If {DEVIATION_PATH} is set (non-empty), read it now:
cat "{DEVIATION_PATH}"
Its "Recommended design fix" section is a hard constraint on the new design. You MUST incorporate it. On re-dispatch you overwrite both design.json and design.md.
Step 1 — Extract the spike brief from the roadmap
Read {ROADMAP_PATH}. Extract the brief for {SPIKE_ID} using this priority order:
First: bullet pattern (primary — the roadmap convention). Under a ### Spike / discovery lane heading (or a heading containing "spike"/"discovery"), find a bullet matching:
- **`{SPIKE_ID}`** — <brief>·- **`{SPIKE_ID}`:** <brief>·- **{SPIKE_ID} IS the spike.** Output: ...
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 · 193 lines · 144 tokens per session scan C f9dadf19cdcd
spike-designer is an agent published in the GitHub repository chris-dare-dev/agent-kit (0 stars, last pushed 2mo ago), licensed MIT. It adds 144 tokens to every session and 2,259 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it C with 2 findings (instruction-override phrasing, reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
editor
Journal editor who desk-reviews manuscripts, selects two referees with deliberately different dispositions, calibrates to a target journal from .claude/references/journal-profiles.md, and synthesizes an editorial decision (FATAL / ADDRESSABLE / TASTE). Used by /review-paper --peer [journal].
Geoprocessing Specialist
ArcPy and Python toolbox expert who automates spatial workflows — builds .pyt toolboxes, Model Builder processes, batch geoprocessing automation, and custom analysis scripts for ArcGIS Pro.
research-scout
Scans the NeqSim codebase to discover scientific paper opportunities that will drive code improvement. Every paper must improve NeqSim — adding tests, validating models against data, hardening algorithms, or implementing new capabilities. Produces ranked, actionable topics that feed into the planner agent.
astronomical-instrumentation-scientist
Reasons from system-level error budgets, the diffraction limit and Strehl ratio, detector figures of merit, and resolving power through Zemax/Code V tolerancing, ETC radiometry, AO modeling, and on-sky standard-star commissioning while treating flexure drift, IR persistence, ghosts, and quasi-static speckles as…
mathodology-problem-analyst
Understand contest questions, requirements, mechanisms and decision needs.
epidemiology-research-agent
Research agent for epidemiology and public health.