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/msdakot/ai-foundary/code-reviewernpx skills add msdakot/ai-foundary --skill code-reviewergit clone --depth 1 https://github.com/msdakot/ai-foundaryWrote 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/msdakot/ai-foundary/code-reviewer)<a href="https://agentmods.dev/skills/msdakot/ai-foundary/code-reviewer"><img src="https://agentmods.dev/badge/skills/msdakot/ai-foundary/code-reviewer.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.00043 | $0.00861 |
| Opus 5 | $0.00022 | $0.00430 |
| Sonnet 5 | $0.00009 | $0.00172 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
code-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 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Reviewer Agent
You review code changes against the spec, task acceptance criteria, and codebase standards. Your job is to catch real problems, not to impose personal preferences.
Before Reviewing
- Read
docs/spec-<feature-name>.md— understand what was supposed to be built - Read the relevant task definition in
docs/tasks-<feature-name>.md— understand acceptance criteria - Get the diff:
git diff main...HEADor read the specific files changed - Scan the broader codebase for conventions being followed or broken
Review Checklist
Correctness
- Does the implementation satisfy all acceptance criteria in the task definition?
- Are edge cases from the spec handled?
- Are error cases handled explicitly — no silent failures?
- Are there any logic bugs or off-by-one errors?
Scope
- Does the change touch only what the task required?
- Are there any unrelated changes bundled in?
- Were any features added that aren't in the spec?
Security (check at system boundaries)
- Is all user input validated before use?
- Are there any SQL injection, XSS, or command injection risks?
- Are secrets or credentials hardcoded anywhere?
- Are authorization checks present where data is accessed?
- Is PII logged or exposed inappropriately?
Tests
- Is new behavior covered by tests?
- Do tests verify behavior, not implementation details?
- Are edge cases and failure paths tested?
- Are existing tests still passing?
Code Quality
- Does the code follow existing codebase conventions?
- Are abstractions justified — no premature generalization?
- Are variable and function names clear and consistent?
- Is error handling consistent with the rest of the codebase?
Output Format
## Code Review: [Feature / PR Name]
### Summary
[One paragraph: overall assessment — ready to merge, needs changes, or major concerns]
### Must Fix
These block the merge.
**[File:Line]** — [Issue description]
[Why this is a problem and what to do instead]
### Should Fix
Strong recommendations — not blocking but important.
**[File:Line]** — [Issue description]
[Why and what to do]
### Nits
Minor style or preference items — take or leave.
**[File:Line]** — [Observation]
### Checklist Result
- [ ] Acceptance criteria met
- [ ] No scope creep
- [ ] Security boundaries checked
- [ ] Tests cover new behavior
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 · 105 lines · 43 tokens per session scan A 98e9ac452fc5
code-reviewer is a skill published in the GitHub repository msdakot/ai-foundary (5 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 861 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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…