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 Fergius-Engineering/instincts --skill independent-review-gategit clone --depth 1 https://github.com/Fergius-Engineering/instinctsWrote 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/fergius-engineering/instincts/independent-review-gate)<a href="https://agentmods.dev/skills/fergius-engineering/instincts/independent-review-gate"><img src="https://agentmods.dev/badge/skills/fergius-engineering/instincts/independent-review-gate/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/fergius-engineering/instincts/independent-review-gate"><img src="https://agentmods.dev/badge/skills/fergius-engineering/instincts/independent-review-gate.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.00023 | $0.00448 |
| Opus 5 | $0.00012 | $0.00224 |
| Sonnet 5 | $0.00005 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
independent-review-gate 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 10d 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
The rule
Your own review and a green test suite are not enough. You're invested in the approach, so you read past your own mistakes, and the tests only cover what you already thought to check. Before calling complex work done, have someone or something with no stake review the whole change.
A fresh set of eyes catches the defect that's obvious in hindsight and invisible to you.
This is the non-optional version of superpowers' requesting-code-review: the review is not a step to skip when the suite is green, because the green suite is exactly what can't be trusted alone — and the fix you make after the review gets re-reviewed too.
Fires when
Finishing a feature or a spec. Before merging. Before claiming "done" on anything non-trivial, or anything that ships to other people.
How to apply
Hand the full diff to an independent reviewer with explicit angles to check: correctness, edge cases, the branches no test touches, backward compatibility. Fix the blockers and cover each one with a test. Then re-review the fix itself — a second pass catches the inverted-fix mistake faster than a new test would.
The green suite is not the gate. The independent verdict is.
Worked example
Your change to a payment client passes all 200 tests and your own read-through. A reviewer with fresh eyes notices that one branch — the error path no test covers — has an inverted condition: it retries on success and gives up on failure.
The suite was green because it only ran the happy path. Your own review missed it because you "knew" what the code was meant to do, so you read what you intended instead of what you wrote.
The independent pass caught it before users did.
Red flags
| Thought | Reality |
|---|---|
| "Tests pass, so it's done" | Tests only cover what you thought to test. |
| "I already reviewed it myself" | You can't see your own blind spot. |
| "It's obviously correct" | The expensive bugs always look obvious until they bite. |
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.
- 10d ago First seen · 39 lines · 23 tokens per session scan A 43e1a1ca71ca
independent-review-gate is a skill published in the GitHub repository Fergius-Engineering/instincts (2 stars, last pushed 16d ago), licensed MIT. It adds 23 tokens to every session and 448 once invoked, about $0.0001 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
memstack-development-code-reviewer
Use this skill when the user says 'review code', 'code review', 'check my code', 'audit this', 'review PR', 'review changes', 'what's wrong with this', or is requesting a structured review of code quality, security, performance, or maintainability. Do NOT use for refactoring plans or test generation.
shard
Use when the user says 'shard this', 'split file', or when working with files over 1000 lines.
audit-agents-skills
Audit Claude Code agents, skills, and commands for quality and production readiness. Use when evaluating skill quality, checking production readiness scores, or comparing agents against best-practice templates.
design-patterns
Detect, suggest, and evaluate GoF design patterns in TypeScript/JavaScript codebases. Use when refactoring code, applying singleton/factory/observer/strategy patterns, reviewing pattern quality, or finding stack-native alternatives for React, Angular, NestJS, and Vue.
pr-triage
4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit…
eval-skills
Audit all skills in the current project for frontmatter completeness, effort level appropriateness, allowed-tools scoping, and content quality. Produces a scored report with effort-level recommendations for each skill. Use when onboarding to a new project, reviewing skill quality before shipping, or adding effort…