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 agentmods add skills/atra-consulting/coding-with-ai-lab/reviewnpx skills add atra-consulting/coding-with-ai-lab --skill reviewgit clone --depth 1 https://github.com/atra-consulting/coding-with-ai-labWrote 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/atra-consulting/coding-with-ai-lab/review)<a href="https://agentmods.dev/skills/atra-consulting/coding-with-ai-lab/review"><img src="https://agentmods.dev/badge/skills/atra-consulting/coding-with-ai-lab/review.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 | $0.00035 | $0.07726 |
| Opus 5 | $0.00017 | $0.03863 |
| Sonnet 5 | $0.00007 | $0.01545 |
| Haiku 4.5 | $0.00003 | $0.00773 |
Grade A, and why
project: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 5d 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 — 825 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Skill
You are executing the review skill, which provides local code review with a multi-round review & fix cycle on a feature branch vs main.
RESULTS DISPLAY GUARANTEE
The skill MUST ALWAYS surface its review results. It never finishes silently. This holds in every mode — embedded (called from plan-and-do) or stand-alone, dry-run or normal.
Every run MUST produce the full review content. One of these two carries it:
- Markdown file — normal mode. The review is written to
[docs_folder]/reviews/REVIEW-<branch>.md(PHASE 6). - On screen — dry-run mode. The full review content is displayed in the conversation instead of writing a file (PHASE 6).
On top of that, the PHASE 7 summary is always printed to screen. In every mode. Including embedded. So the caller and the user both see the outcome.
Embedded mode skips only PHASE 0 (plan-mode check and header) and PHASE 1.3 (task-understanding confirmation). It still runs PHASE 6 and PHASE 7. So it still writes the review file and prints the summary.
If a run reaches the end without producing either the Markdown file or the on-screen content, that is a bug. Produce the on-screen content before stopping.
Writing Style
Short and brief. Short sentences. Simple words non-native speakers understand. No passive voice. Use sentence fragments.
FILE PATH DISPLAY RULE
When displaying any file path to the user, ALWAYS use the full absolute path. Get the project root with pwd and prepend it to relative paths. Example: /Users/dev/project/docs/reviews/REVIEW-add-feature.md instead of docs/reviews/REVIEW-add-feature.md. This lets users Command-click paths in the terminal to open them.
HOW TO ASK THE USER FOR DECISIONS
Use the AskUserQuestion tool for all user prompts. This is the built-in tool that pauses execution and waits for the user to type a response.
Numbered choices: Pass the full question text (including numbered options) as the question parameter.
Freeform input: Pass the question as the question parameter.
What ships with it
1 file 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.
- 5d ago First seen · 825 lines · 35 tokens per session scan A b6346a5b22cf
project:review is a skill published in the GitHub repository atra-consulting/coding-with-ai-lab (5 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 7,726 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…