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 agentmods add skills/ahernandez-developer/claude-crap/check-testnpx skills add ahernandez-developer/claude-crap --skill check-testgit clone --depth 1 https://github.com/ahernandez-developer/claude-crapWrote 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/ahernandez-developer/claude-crap/check-test)<a href="https://agentmods.dev/skills/ahernandez-developer/claude-crap/check-test"><img src="https://agentmods.dev/badge/skills/ahernandez-developer/claude-crap/check-test.svg" alt="Measured on agentmods" 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 | $0.00192 | $0.01092 |
| Opus 5 | $0.00096 | $0.00546 |
| Sonnet 5 | $0.00038 | $0.00218 |
| Haiku 4.5 | $0.00019 | $0.00109 |
Grade A, and why
check-test 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check the test harness for a file
Run the require_test_harness MCP tool from the claude-crap server against a user-supplied file path and report whether a matching test exists.
Arguments
The user supplies a file path as the argument, typed after the skill name:
/claude-crap:check-test src/foo/bar.ts
/claude-crap:check-test pkg/mod.py
/claude-crap:check-test app/src/main/java/com/example/Service.java
Pass $ARGUMENTS verbatim as the filePath argument to the MCP tool. Do not normalize, strip quotes, or resolve the path yourself — the server's workspace guard handles that.
Steps
- Invoke the MCP tool
require_test_harnesswithfilePath: "$ARGUMENTS". - If the tool returns
hasTest: true:- Tell the user the test file path from the
testFilefield, formatted as a clickable relative path. - If
isTestFile: true, note that the user's input was itself already a test file — the resolver short-circuited. This usually means the user meant to ask about a different file; suggest they re-run the skill with the production file path.
- Tell the user the test file path from the
- If the tool returns
hasTest: false:- Tell the user no matching test was found.
- Remind them that CLAUDE.md's Golden Rule forbids writing functional code in this file until a characterization test exists — that's the plugin's core contract.
- List the first 3 paths from the
candidatesarray as suggested locations for the new test. These are ordered by the resolver's convention priority: sibling<name>.test.<ext>first, then__tests__/<name>.test.<ext>, then mirror-tree layouts undertests/,test/, and__tests__/at the workspace root, then the nearest-ancestor flattests/directory, then Pythontest_<name>.pyvariants. Suggest the highest-priority candidate that matches the project's existing conventions — if you can see other test files in the repo, pick the layout that matches them.
- If the tool returns an error (
status: "error"):- The most common cause is a path that escapes the workspace root. Tell the user to use a workspace-relative path (e.g.
src/foo.ts, not../other-repo/foo.ts). - The second-most-common cause is a typo in the file path. Ask them to double-check the path exists.
- The most common cause is a path that escapes the workspace root. Tell the user to use a workspace-relative path (e.g.
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.
- 4d ago First seen · 51 lines · 192 tokens per session scan A e5c034500367
check-test is a skill published in the GitHub repository ahernandez-developer/claude-crap (8 stars, last pushed 4mo ago), licensed MIT. It adds 192 tokens to every session and 1,092 once invoked, about $0.0010 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…