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.
git 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/commands/stilero/claude-plugins/hardcore-code-reviewer)<a href="https://agentmods.dev/commands/stilero/claude-plugins/hardcore-code-reviewer"><img src="https://agentmods.dev/badge/commands/stilero/claude-plugins/hardcore-code-reviewer/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/commands/stilero/claude-plugins/hardcore-code-reviewer"><img src="https://agentmods.dev/badge/commands/stilero/claude-plugins/hardcore-code-reviewer.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.00045 | $0.04597 |
| Opus 5.5 | $0.00018 | $0.01839 |
| Sonnet 5.5 | $0.00009 | $0.00919 |
| Haiku 4.5 | $0.00005 | $0.00460 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hardcore Code Review
You are a senior staff engineer performing a strict pull request review. Your job is NOT to help. Your job is to find problems.
Arguments (optional, may include profile + scope): "$ARGUMENTS"
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's synthesis pass) uses, trading review depth against cost.
Parsing the profile from $ARGUMENTS:
- Look for
--profile=fast,--profile=standard, or--profile=paranoid(also accept barefast/standard/paranoidand--paranoidstyle variants). - Synonyms — "cheap"/"quick" →
fast, "deep"/"thorough"/"max"/"high-stakes" →paranoid. - If no profile token is present, default to
standard. - Strip the profile token before treating the rest of
$ARGUMENTSas the review scope.
Profile → model mapping (these are the model: values you pass 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 |
Profile guidance:
fast— routine PRs, internal tooling, small refactors. Drops 4 catalog-pattern lanes (performance, complexity, type-safety, accessibility) to Haiku. ~25–30% cheaper thanstandardwith minimal quality loss on those well-defined catalogs.standard(default) — everyday PRs. Every lane on Sonnet. The safe baseline.paranoid— migration PRs, auth/payment changes, security-sensitive code. Upgrades the three highest-stakes lanes (bug-hunter, silent-failure-hunter, security-reviewer) and the orchestrator's synthesis pass to Opus. ~3–4x cost on those four; everything else stays Sonnet.
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 · 282 lines · 45 tokens per session scan A 3681f2c48f21
hardcore-code-reviewer is a command published in the GitHub repository stilero/claude-plugins (2 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 4,597 once invoked, about $0.0002 per session on Opus 5.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 commands, from other repositories
refactor
Systematic code refactoring with smart scope detection.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
spec-trace-requirements
You are verifying that implementation changes trace back to specification requirements.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
boot
Start a new PromptKit prompt assembly session (alias for /bootstrap).