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 stepanenkoviktor0110-boop/ai-dev-methodology-codex --skill code-reviewinggit clone --depth 1 https://github.com/stepanenkoviktor0110-boop/ai-dev-methodology-codexWrote 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/stepanenkoviktor0110-boop/ai-dev-methodology-codex/code-reviewing)<a href="https://agentmods.dev/skills/stepanenkoviktor0110-boop/ai-dev-methodology-codex/code-reviewing"><img src="https://agentmods.dev/badge/skills/stepanenkoviktor0110-boop/ai-dev-methodology-codex/code-reviewing.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.00064 | $0.02185 |
| Opus 5 | $0.00032 | $0.01092 |
| Sonnet 5 | $0.00013 | $0.00437 |
| Haiku 4.5 | $0.00006 | $0.00218 |
Grade A, and why
code-reviewing 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 7d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 7d ago First seen · 239 lines · 64 tokens per session scan A 0a411ebd4e76
code-reviewing is a skill published in the GitHub repository stepanenkoviktor0110-boop/ai-dev-methodology-codex (1 stars, last pushed 4mo ago), with no licence file. It adds 64 tokens to every session and 2,185 once invoked, about $0.0003 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
joycraft-design
Design discussion before decomposition — produce a 200-line design artifact for human review, catching wrong assumptions before they propagate into specs.
joycraft-spec-done
Lightweight per-spec wrap-up — bump status to in-review, terse discovery if surprised, commit. Run after each spec in checkpoint/isolated mode; no validation, no push, no PR.
typescript-quality-enforcer
Audit and strengthen TypeScript/JavaScript type-evidence and lint discipline, stage adoption of deterministic anti-slop Oxlint rules, and remediate approved violations without laundering diagnostics. Use when a repository needs stronger TypeScript/JavaScript quality enforcement, unsafe type escape-hatch cleanup…
review-and-refactor-code
Review a defined diff or code area for actionable defects and integration risks, assess structural problems, and plan or execute behavior-preserving refactors through traceable evidence and incremental verification. Use when a user asks for code review, change-risk analysis, maintainability assessment, cleanup…
8eyes
Multi-agent adversarial code review via eight-eyes enforcement kernel.
code-review-excellence
This skill should be used when the user asks to review a diff or pull request, write review comments, audit code quality, establish review standards, or improve how a team performs code review.