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 sjh9714/red-handed --skill historygit clone --depth 1 https://github.com/sjh9714/red-handedWrote 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/sjh9714/red-handed/history)<a href="https://agentmods.dev/skills/sjh9714/red-handed/history"><img src="https://agentmods.dev/badge/skills/sjh9714/red-handed/history/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/sjh9714/red-handed/history"><img src="https://agentmods.dev/badge/skills/sjh9714/red-handed/history.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.00075 | $0.00449 |
| Opus 5 | $0.00037 | $0.00225 |
| Sonnet 5 | $0.00015 | $0.00090 |
| Haiku 4.5 | $0.00007 | $0.00045 |
Grade A, and why
history 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 12d 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.
What it actually says
Audit every session on this machine
npx --yes @jinhyuk9714/red-handed@latest stats
Add --lang ko for a Korean report, --since 30 to limit it to the last 30
days, --json to read the numbers rather than quote them, --no-cache to
recompute from scratch.
The first run reads every transcript; later runs are near-instant because the
results are cached in ~/.red-handed/cache.json (mode 0600, on this machine
only, relocatable with RED_HANDED_HOME).
What to report
The headline is the coverage count, which everyone gets whether or not anything was found:
184 sessions. Your agent said "tests pass" 84 times.
79 a test ran first
5 no test ran in that session at all
Quote it as printed. Then note how many findings there were, if any.
Two things to keep straight when the user reads their own number:
- "No test ran in that session" is not proof of a lie. Verification this tool
cannot read — a project's own runner, a browser check — counts as verification
it did not see. That is why those land at
SUSPICIOUSrather thanCAUGHT. - A count of zero at the
CAUGHTtier is a real result, not an empty one. The tool is built to miss things rather than to accuse wrongly.
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.
- 12d ago First seen · 43 lines · 75 tokens per session scan A f9947946fb10
history is a skill published in the GitHub repository sjh9714/red-handed (4 stars, last pushed 1mo ago), licensed MIT. It adds 75 tokens to every session and 449 once invoked, about $0.0004 per session on Opus 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 skills, from other repositories
tdd
A test-driven development workflow based on repeating three stages: write a failing test, make it pass, then improve the code. The tests focus on what users can do through public interfaces rather than internal implementation details.
bug-fix
A structured bug-fixing workflow that takes a problem from reproduction and evidence-based cause finding through approval, implementation, testing, and cleanup.
skill-test
Verifies that the skill system is working correctly.
tdd
Test-driven development — write the failing test first, then the code. Triggers on TDD, test first, write tests, test-driven.
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…
agent-reproduce-align
Use after a Codex or Claude Code feature has been implemented in Qwen Code to run the selected reference agent and Qwen Code under the same scenario, capture HTTP and terminal traces, compare request bodies, tool/function schemas, outputs, and iterate until the reproduced behavior is close enough.