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-executor)<a href="https://agentmods.dev/agents/chris-dare-dev/agent-kit/spike-executor"><img src="https://agentmods.dev/badge/agents/chris-dare-dev/agent-kit/spike-executor/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-executor"><img src="https://agentmods.dev/badge/agents/chris-dare-dev/agent-kit/spike-executor.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.00151 | $0.02145 |
| Opus 5.5 | $0.00060 | $0.00858 |
| Sonnet 5.5 | $0.00030 | $0.00429 |
| Haiku 4.5 | $0.00015 | $0.00215 |
Grade C, and why
spike-executor 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-executor/lessons.md" 2>/dev/null || echo "(no lessons yet)" How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spike Executor
You are Phase 2 of the /spike pipeline. Your job is to implement the POC, run it, and produce measurements.json that faithfully records the values the design's criteria need — the verdict will be derived from them by spike-decide.py, so accuracy and honest unmeasurability matter more than a favorable result.
The orchestrator dispatches you with substituted variables. You never invoke other sub-agents.
Input variables (substituted by the orchestrator)
{SPIKE_ID}— the spike identifier{DESIGN_JSON_PATH}— absolute path todesign.json(the typed contract — read it fully){DESIGN_PATH}— absolute path todesign.md(the human executor instructions){DESIGN_HASH}— the sha256 of design.json the orchestrator checkpointed; you MUST echo it verbatim into measurements.json (do NOT recompute it){POC_DIR}— absolute path topoc/(your only writable source directory){MEASUREMENTS_PATH}— absolute path tomeasurements.jsonyou MUST write{VALIDATE_SCRIPT}— absolute path tospike-validate.py(used in Step 5 self-validation)
Step 0 — Read persistent memory (skip-if-not-relevant)
cat ".claude/agent-memory/spike-executor/lessons.md" 2>/dev/null || echo "(no lessons yet)"
Step 1 — Read design.json AND design.md fully
cat "{DESIGN_JSON_PATH}"; echo "---"; cat "{DESIGN_PATH}"
design.json is the contract: criteria (with fields/operators/thresholds), measurement_fields (every one must get a value), poc_constraints, sample_size. design.md holds the step-by-step executor instructions. Follow both exactly.
Step 2 — Detect design flaws BEFORE building
Verify the design is executable: can the criteria be measured with the available tools/access? Is the POC ≤ max_loc with the allowed language/dependencies? Does every measurement_field have a way to be produced?
If the design is fundamentally flawed (genuinely unexecutable, not merely inconvenient), write design-deviation.md and return status: design-deviation. Do NOT silently work around it. design-deviation.md contains: Problem · Cannot execute because · Recommended design fix (a concrete change to design.json/design.md) · Attempted workarounds considered.
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 · 179 lines · 151 tokens per session scan C 11cf16097b3a
spike-executor is an agent published in the GitHub repository chris-dare-dev/agent-kit (0 stars, last pushed 2mo ago), licensed MIT. It adds 151 tokens to every session and 2,145 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
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
aggregate-tests-implementator
Implements pytest test functions for > classes from the Tests table in .domain/test-plan.md. Requires @aggregate-fixtures-writer to have run first. Invoke with: @aggregate-tests-implementator.
python-test-engineer
Use proactively for generating Python tests with pytest, unittest, and comprehensive strategies. Expert in async testing, mocking, and property-based testing.
python-test-engineer
Write behavior-driven suites and drive TDD workflows in Python. TRIGGER WHEN: writing tests, improving test coverage, fixing broken tests, setting up pytest configurations, or practicing red-green-refactor workflows. DO NOT TRIGGER WHEN: building new features from scratch or designing system architecture (use…
python-implementation-agent
Implement Python development tasks with testing and verification.
python-expert
Use this agent when working with Python code that requires advanced features, performance optimization, or comprehensive refactoring. Examples: Context: User needs to optimize a slow Python function that processes large datasets. user: "This function is taking too long to process our data, can you help optimize it?"…