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-reviewgit 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)<a href="https://agentmods.dev/skills/dds-solutions/ai-tadpole-os/code-review"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/code-review/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/dds-solutions/ai-tadpole-os/code-review"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/code-review.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.00042 | $0.01266 |
| Opus 5.5 | $0.00017 | $0.00506 |
| Sonnet 5.5 | $0.00008 | $0.00253 |
| Haiku 4.5 | $0.00004 | $0.00127 |
Grade A, and why
code-review 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 3d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[!IMPORTANT] AI Context & Knowledge Heritage
- Subsystem: Agent Skills Registry / code-review
- Architecture:
@docs ARCHITECTURE:Documentation- Failure Path: Merged-axis bias, unverified requirement coverage, ungrounded review comments.
- Observability: Traceability via
execution/parity_guard.py([SKILL])
Two-Axis Code Review Protocol
Review the diff between HEAD and a fixed point along two distinct, un-merged axes:
- Standards Axis: Does the code conform to documented repo standards, clean-code invariants, and Fowler code smells?
- Spec Axis: Does the code faithfully implement the originating issue, blueprint, or PRD requirements?
Both axes run as parallel sub-agents so that cognitive bias from one axis does not pollute the other.
📚 Progressive Disclosure & L3 Reference Index
Consult deep L3 Reference Guides and verification tools on demand:
- Fowler Smells Catalog & Two-Axis Architecture: fowler_code_smells_and_two_axis_review.md
- Deterministic Two-Axis Reviewer: two_axis_reviewer.py
1. Pin the Fixed Point
Before initiating review, establish a deterministic baseline:
- Determine the fixed point (commit SHA, branch, tag,
main,HEAD~5). - Verify resolution:
git rev-parse <fixed-point>. - Capture diff once:
git diff <fixed-point>...HEAD(three-dot comparison against merge-base). - Capture commit log:
git log <fixed-point>..HEAD --oneline.
2. Identify Review Sources
Spec Source
Locate the originating requirements in priority order:
- Issue references in commit messages (
#123,Closes #45). - A blueprint, spec, or PRD file passed in conversation or found under
docs/,specs/, or.tmp/. - If no spec is found, note "No spec available" and skip the Spec sub-agent.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago Changed · +26 lines · -1 tokens per session 665f30a70f41
- 1mo ago First seen · 80 lines · 43 tokens per session scan A 5e1ff661e68c
code-review is a skill published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed 3d ago), licensed MIT. It adds 42 tokens to every session and 1,266 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 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.
review-external-prs
Triage open solana-foundation/solana-com pull requests from non-member authors with gh, screen every submission for scams and low-trust products, enforce the repository's signed-and-squashed commit requirement, safely close ineligible cruft when authorized, and write a maintainer report. Use when asked to review…
react-application-structure
Establishes or reviews the directory layout, feature boundaries, state design, routing approach, and data-fetching conventions for a React 18+ TypeScript application. Invoked when the user asks to structure a React app, set up a scalable architecture, or review React project organization.
next-application-structure
Establishes or reviews directory layout, server/client boundaries, routing, data-fetching strategy, and testing structure for Next.js 14+ App Router TypeScript applications. Invoked when the user asks to structure a Next app, set App Router conventions, or review architecture for React parity.