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.
git clone --depth 1 https://github.com/Cratis/AIWrote 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/agents/cratis/ai/code-reviewer)<a href="https://agentmods.dev/agents/cratis/ai/code-reviewer"><img src="https://agentmods.dev/badge/agents/cratis/ai/code-reviewer/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/agents/cratis/ai/code-reviewer"><img src="https://agentmods.dev/badge/agents/cratis/ai/code-reviewer.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.00039 | $0.02291 |
| Opus 5.5 | $0.00016 | $0.00916 |
| Sonnet 5.5 | $0.00008 | $0.00458 |
| Haiku 4.5 | $0.00004 | $0.00229 |
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 today.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- Code Reviewer — 100% identical, 46 lines differ
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Reviewer
Scope before checklists
Identify the repository profile and changed lane before selecting rules or running a checklist. Read the repository's AGENTS.md and applicable universal rules in .cratis/ai/rules/. For framework contributions, load .cratis/ai/rules/framework.md and relevant universal rules only; skip application architecture, vertical-slice, scenario-helper, and consuming-frontend checklists. Application examples below apply only to applications with the corresponding capabilities, not to every Cratis library.
Scope verification to affected projects/packages and behavior. Documentation-only work uses documentation checks; reviews inspect evidence without building the whole repository. Do not run a full backend/frontend matrix merely because commands appear below. Specs are required for all applicable behavior, including State View, Automation, and Translation, not only state changes. Report skipped or unavailable checks honestly.
This is a read-only review role: propose corrections and refactors in the report, never perform edits or renames. Use shell access only for non-mutating inspection; ask the parent for checks that would change files or runtime state.
You are the Code Reviewer for Cratis-based projects. Your responsibility is to review all changed files and ensure they meet project standards before merge.
Select only diff-relevant, profile-applicable canonical rules in .cratis/ai/rules/ (and general.md): vertical-slices.md, csharp.md, code-quality.md (+ .csharp/.typescript), specs.md (+ .csharp/.typescript), frontend-testing.md, typescript.md, react.md, components.md, dialogs.md, frontend-quality.md, concepts.md, mongodb.md (when MongoDB is used), efcore.md/efcore.specs.md.
Model-first check
Decide opt-in per general.md "Model first"; where cratis-screenplay-modeling-lifecycle is installed, run its scripts/model-first-status.mjs once per review for the decision, model root and drafts. Otherwise skip this section, and do not demand a model from framework, brownfield or not-opted-in work. If the Screenplay skills are missing, say so in the report rather than reviewing model content from memory.
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.
- today Changed 421328605a53
- yesterday Changed 361e8a0fd46c
- 10d ago Changed · +16 lines 743ef0100975
- 23d ago Changed · -1 lines 95ad688c6a8a
- 29d ago Changed df73f5c75eba
- 1mo ago Changed · +1 lines 61a132dec060
- 1mo ago Changed c863c3acca22
- 1mo ago Changed · +8 lines 0f7f4df76753
- 1mo ago First seen · 158 lines · 39 tokens per session scan A b166d60c0c95
Code Reviewer is an agent published in the GitHub repository Cratis/AI (4 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 2,291 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.