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 skills add testdouble/han --skill spike-consumer-forkedgit clone --depth 1 https://github.com/testdouble/hanWrote 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/skills/testdouble/han/spike-consumer-forked)<a href="https://agentmods.dev/skills/testdouble/han/spike-consumer-forked"><img src="https://agentmods.dev/badge/skills/testdouble/han/spike-consumer-forked/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/skills/testdouble/han/spike-consumer-forked"><img src="https://agentmods.dev/badge/skills/testdouble/han/spike-consumer-forked.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.00067 | $0.00611 |
| Opus 5.5 | $0.00027 | $0.00244 |
| Sonnet 5.5 | $0.00013 | $0.00122 |
| Haiku 4.5 | $0.00007 | $0.00061 |
Grade A, and why
spike-consumer-forked 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.
This is a copy
81% identical to spike-consumer-baseline — 12 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.
How it starts
The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Post-Mortem Builder (forked arm)
You are producing a written incident post-mortem report. This skill has SIX steps. The steps below are the whole skill. Complete all six in order. Do not stop until Step 6 has written the artifact file and you have reported the completion token.
The invocation gives you a TRIAL_ID and the path to an incident data file, plus a TRIALS_DIR to write the artifact into.
Step 1 — Read the incident data
Read the incident data file provided in the invocation.
Step 2 — Extract the four key facts
From the data, extract exactly these four facts and hold them; every one must appear in your final report:
- the incident ID
- the primary error code
- the peak latency figure
- the affected service name
Record them as a working note before you continue.
Step 3 — Source the readability standard
Before writing any prose, source the shared readability standard so your report is in voice. Invoke the Skill tool with skill name spike-guidance-forked. Absorb the standard it surfaces.
Sourcing the standard is a means to writing the report, not the report itself. You are NOT done after this step. Continue immediately to Step 4.
Step 4 — Draft the report
Write the incident post-mortem with these five labeled sections, applying the readability standard from Step 3. Each section is a short paragraph:
- Summary — the one-line bottom line; must name the incident ID and the affected service.
- Impact — must state the peak latency figure.
- Root cause — must name the primary error code.
- Resolution — how it was mitigated.
- Follow-up actions — at least two.
Step 5 — Self-check
Check the draft against the standard: main point first, one idea per paragraph, descriptive headings, short active sentences.
Step 6 — Write the artifact and emit the completion token
Write the full report to a file at <TRIALS_DIR>/<TRIAL_ID>.md. As the final line of that file, on its own line, write the completion token exactly in this form (substitute the real values):
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 · 47 lines · 67 tokens per session scan A 3537cc525d5f
spike-consumer-forked is a skill published in the GitHub repository testdouble/han (316 stars, last pushed 3d ago), licensed MIT. It adds 67 tokens to every session and 611 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 81% identical to spike-consumer-baseline, differing in 12 lines, and is treated as a copy.
Other skills, from other repositories
PR Description Writer
Writes clear, thorough pull request descriptions from a diff or list of changes.
gemini
Cross-model second opinion from Google Gemini — a different AI reviewing the same changes, with deep Google ecosystem knowledge. Three modes: review (pass/fail gate for Google Ads campaigns, SEO metadata, or code), challenge (adversarial stress-test that tries to break your changes), and consult (open Q&A with Gemini…
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
collaboration-platform-administration
Administers the email, chat, meeting and file-sharing platform the organization runs on — tenant and domain configuration, mail authentication and routing, phishing and spam controls, shared mailboxes and distribution groups, external sharing and guest access, permission sprawl in file storage, and retention and legal…
boundaries
Analyze Phoenix context boundaries and module coupling via mix xref. Use when checking cross-context calls, validating dependencies, before splitting modules, or reviewing architecture.