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 DDS-Solutions/AI-TadPole-OS --skill code-review-checklistgit clone --depth 1 https://github.com/DDS-Solutions/AI-TadPole-OSWrote 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/dds-solutions/ai-tadpole-os/code-review-checklist)<a href="https://agentmods.dev/skills/dds-solutions/ai-tadpole-os/code-review-checklist"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/code-review-checklist.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.1 | $0.00017 | $0.01564 |
| Opus 5 | $0.00009 | $0.00782 |
| Sonnet 5 | $0.00003 | $0.00313 |
| Haiku 4.5 | $0.00002 | $0.00156 |
Grade A, and why
code-review-checklist 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 8d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This rewrite transforms the Code Review Checklist from a passive list of tips into a Rigorous Audit Engine.
I have integrated it directly into the REVIEW mode of the behavioral-modes skill and the standards of the clean-code skill. I also added a "Sovereign Context" section to handle the difference between new and legacy code, ensuring the AI doesn't waste time over-engineering old files while remaining ruthless with new ones.
Revised SKILL.md
--- File: SKILL.md
name: code-review-checklist
description: Professional audit rubric for code quality, security, and performance. Mandatory for all REVIEW mode operations.
when_to_use: "When executing REVIEW mode, auditing PRs, performing security scans, or validating a feature before it enters SHIP mode."
allowed-tools: Read, Write, Glob, Grep, Execute
version: 2.0
priority: CRITICAL
🛡️ Code Review Audit Engine
This skill is the Audit Engine for the REVIEW behavioral mode. It ensures that all code entering the production pipeline meets the "Sovereign Reality" standard of excellence.
⛓️ Pipeline Integration
This skill is the "Judge" in the PEC (Plan-Execute-Critic) loop:
IMPLEMENT $\rightarrow$ REVIEW (This Skill) $\rightarrow$ DEBUG (If flaws found) $\rightarrow$ SHIP
📏 The Sovereign Standard (Contextual Auditing)
The AI must adjust its severity based on the Code Context:
| Context | Review Rigor | Primary Goal | Rule |
|---|---|---|---|
| Greenfield (New Code) | 🔴 Ruthless | Perfect Architecture | Zero tolerance for clean-code violations. |
| Feature Update | 🟡 Strict | Stability & Parity | New code must be perfect; existing code must not degrade. |
| Legacy Fix | 🟢 Pragmatic | Risk Mitigation | Boy Scout Rule: Leave it better than you found it, but don't rewrite the world. |
📋 The Master Audit Rubric
1. Correctness & Logic
- Functional Parity: Does the code actually solve the problem stated in
BRAINSTORM? - Edge Case Resilience: Handled
null,undefined, timeouts, and empty states? - Aletheia Validation: Does the logic follow a verifiable path, or is there "wishful thinking"?
- Error Handling: Are errors caught, logged, and handled gracefully (not just
console.log)?
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.
- 8d ago First seen · 136 lines · 17 tokens per session scan A 812aa73e6eee
code-review-checklist is a skill published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 1,564 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
walkeros-understanding-development
Use when contributing to walkerOS, before writing code, or when unsure about project conventions. Covers build/test/lint workflow, XP principles, folder structure, and package usage.
architecture-audit
Systematic architecture audit and refactoring methodology for Rust + TypeScript codebases. Use when performing refactoring, cleanup, unification, code review, dead code removal, module reorganization, or tech debt elimination. Ensures no naming confusion, semantic overloading, hidden defaults, duplicate logic, or…
react-frontend
React, TypeScript, and Next.js patterns for frontend development. Use when building React components, managing state, fetching data, optimizing performance, or working with Next.js App Router. Covers React 18-19, hooks, Server Components, and type-safe patterns.
critic-contract
Shared read-side contract every read-only CRITIC imports — adversarial stance, empirical verification of runtime-behavior claims, the mandatory self-red-team before APPROVE, how a finding is stated (quote the span, take the UNKNOWN escape hatch) and held (only new evidence moves a severity, never pushback), spec-UB…
code-quality
Shared clean-code / DRY / KISS / YAGNI standards and stack-specific smells for the React 19 + TypeScript + Rust (Tauri 2) monorepo. Library consumed by the code-quality-reviewer and code-quality-author agents.
review-workflow
The implement→review flow under the ≤3-reviewer budget with the conditional test stage. Use for /implement-feature, /fix-bug, /refactor-module and any change that needs structured review.