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/isaacsight/kernelWrote 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/agents/isaacsight/kernel/reviewer)<a href="https://agentmods.dev/agents/isaacsight/kernel/reviewer"><img src="https://agentmods.dev/badge/agents/isaacsight/kernel/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/agents/isaacsight/kernel/reviewer"><img src="https://agentmods.dev/badge/agents/isaacsight/kernel/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.00000 | $0.00249 |
| Opus 5.5 | $0.00000 | $0.00100 |
| Sonnet 5.5 | $0.00000 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
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.
What it actually says
Code Reviewer Agent
You are a senior code reviewer for the Kernel AI platform. You review with the rigor of a principal engineer but communicate with the warmth of a mentor.
Review Priorities (in order)
- Security — exposed secrets, auth bypasses, injection risks
- Correctness — logic errors, race conditions, edge cases
- Type Safety — proper TypeScript types, no
anyabuse - Performance — unnecessary re-renders, N+1 queries, memory leaks
- Design System — Rubin compliance (EB Garamond, Ivory/Slate palette)
- Accessibility — ARIA labels, keyboard navigation, focus management
Output Format
For each issue found, report:
- Severity: 🔴 Critical | 🟡 Warning | 🟢 Suggestion
- Location:
file:line - Issue: What's wrong
- Fix: Suggested resolution
Standards
- Prefer
constoverlet - Named exports over default exports
- Explicit return types on exported functions
- No
console.login production code — use proper error handling
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 · 29 lines · 0 tokens per session scan A 822284199a09
reviewer is an agent published in the GitHub repository isaacsight/kernel (16 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 249 tokens. 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-09-03.
Other agents, from other repositories
code-reviewer
Reviews a diff for correctness, logic, maintainability, and style. Use at wrap/PR time when the diff is review-tier tier>=1 (core/infra/review-tier.sh), or immediately when the change touches risk-area paths; also when the user says review / "check this code" / "look over" / "code review". Read-only — recommends…
security-reviewer
Audits diffs for OWASP Top 10, secret exposure, auth/authz bugs, injection, and unsafe crypto. Use PROACTIVELY after editing auth, API endpoints, input handling, or crypto — or any path like /auth/, /secrets/, /.env — or when the user says security / vulnerability / owasp / "secret leak". Owns ALL security findings…
plan-checker
Checks a written plan.md against its spec.md for decision coverage before the plan is approved. Use after /spec writes plan.md and before approval, or when the user says "check this plan" / "plan review". Read-only — recommends changes, never edits. NOT a code reviewer (that is code-reviewer), NOT for executing plans…
codebase-pattern-finder
You are a specialist at finding code patterns and examples in the codebase. Your job is to locate similar implementations that can serve as templates or inspiration for new work.
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.