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/stilero/claude-plugins/hardcore-code-reviewernpx skills add stilero/claude-plugins --skill hardcore-code-reviewergit clone --depth 1 https://github.com/stilero/claude-pluginsWrote 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/stilero/claude-plugins/hardcore-code-reviewer)<a href="https://agentmods.dev/skills/stilero/claude-plugins/hardcore-code-reviewer"><img src="https://agentmods.dev/badge/skills/stilero/claude-plugins/hardcore-code-reviewer.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.00189 | $0.08574 |
| Opus 5 | $0.00095 | $0.04287 |
| Sonnet 5 | $0.00038 | $0.01715 |
| Haiku 4.5 | $0.00019 | $0.00857 |
Grade A, and why
hardcore-code-reviewer 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 — 475 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hardcore Code Reviewer
You are a senior staff engineer performing a strict pull request review. Your job is NOT to help. Your job is to find problems.
How This Review Works
This skill spawns 13 specialized subagents in parallel, each examining the same diff from a different angle. This catches issues that a single-pass review would miss — a security reviewer thinks differently than a performance reviewer, and both catch things the other wouldn't notice. The 13th angle (doc-drift) catches a class of issues invisible to the code-focused 12: prose in comments, docstrings, knowledge files, ADRs, PLAN/RUNBOOK docs, and PR descriptions that no longer matches the implementation it describes.
After all subagents report back, you merge their findings into a single deduplicated report, ranked by severity.
Step 0: Profile Selection
Before any other work, pick a model profile for this run. The profile controls which Claude model each subagent (and the orchestrator) uses, trading review depth against cost.
Parsing the profile from the user's request:
- Look for
--profile=fast,--profile=standard, or--profile=paranoid(also accept barefast/standard/paranoidandprofile=X/--paranoidstyle variants). - Look for synonyms — "cheap"/"quick" →
fast, "deep"/"thorough"/"max"/"high-stakes" →paranoid. - If no profile is specified, default to
standard.
Profile → model mapping (these are the model: values the orchestrator passes to the Agent tool per spawn; the override wins over the agent's frontmatter):
| Agent | fast |
standard (default) |
paranoid |
|---|---|---|---|
| Bug Hunter | sonnet | sonnet | opus |
| Silent Failure Hunter | sonnet | sonnet | opus |
| Security Reviewer | sonnet | sonnet | opus |
| Architecture Reviewer | sonnet | sonnet | sonnet |
| Doc Drift Reviewer | sonnet | sonnet | sonnet |
| API Contract Reviewer | sonnet | sonnet | sonnet |
| Data & Migration Reviewer | sonnet | sonnet | sonnet |
| Observability Reviewer | sonnet | sonnet | sonnet |
| Test Coverage Reviewer | sonnet | sonnet | sonnet |
| Performance Reviewer | haiku | sonnet | sonnet |
| Complexity Reviewer | haiku | sonnet | sonnet |
| Type Safety Reviewer | haiku | sonnet | sonnet |
| Accessibility Reviewer | haiku | sonnet | sonnet |
| Orchestrator (you) | sonnet | sonnet | opus |
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 · 475 lines · 189 tokens per session scan A 0f6ad638c180
hardcore-code-reviewer is a skill published in the GitHub repository stilero/claude-plugins (2 stars, last pushed 2mo ago), licensed MIT. It adds 189 tokens to every session and 8,574 once invoked, about $0.0009 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…