Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/aawwcc/ape/spike-researcher)<a href="https://agentmods.dev/agents/aawwcc/ape/spike-researcher"><img src="https://agentmods.dev/badge/agents/aawwcc/ape/spike-researcher/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/aawwcc/ape/spike-researcher"><img src="https://agentmods.dev/badge/agents/aawwcc/ape/spike-researcher.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.00011 | $0.00198 |
| Opus 5 | $0.00005 | $0.00099 |
| Sonnet 5 | $0.00002 | $0.00040 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
spike-researcher 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 8d 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.
This is a copy
95% identical to debugger — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Read ${CLAUDE_PLUGIN_ROOT}/prompts/common.md and
${CLAUDE_PLUGIN_ROOT}/prompts/spike_researcher.md, then execute the supplied StageTicket exactly.
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.
- 8d ago First seen · 10 lines · 11 tokens per session scan A 6ee396f50fb5
spike-researcher is an agent published in the GitHub repository AAWWCC/ape (0 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 198 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to debugger, differing in 8 lines, and is treated as a copy.
Other agents, from other repositories
sdd-apply
Implement SDD tasks with strict TDD evidence and review workload guard.
sdd-verify
Verify implementation against SDD specs, tasks, strict TDD evidence, and review workload boundaries.
ap-implementer
L3 executor - G4 IMPLEMENT. Builds one feature from its approved executable roadmap item or conditional frozen plan using strict TDD and real test runs; coverage >=95% on changed lines. Reports PLAN-CONFLICT rather than improvising.
frontend-author
Use when writing or modifying frontend/UI code. Owns the TDD workflow, component conventions, state management, and UI security. MUST write failing tests before implementation code. Reads tech stack from {{PROJECTDIR}}/.codearbiter/tech-stack.md.
tdd-executor
Executes a single task through the full 6-phase TDD workflow (Understand, Write Tests, RED, Implement, GREEN, Complete). Manages the RED-GREEN-REFACTOR cycle autonomously with phase gate enforcement and regression protection.
dev-tdd
TDD development with Red-Green-Refactor cycle, plus generating tests for existing code and setting up test infrastructure. Use to implement a feature by writing tests BEFORE the code, to back-fill a test suite on existing code, or to configure the test framework/coverage/CI. Trigger automatically when the user asks…