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/big-emotion/agent-atelierWrote 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/big-emotion/agent-atelier/code-review)<a href="https://agentmods.dev/agents/big-emotion/agent-atelier/code-review"><img src="https://agentmods.dev/badge/agents/big-emotion/agent-atelier/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/agents/big-emotion/agent-atelier/code-review"><img src="https://agentmods.dev/badge/agents/big-emotion/agent-atelier/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.00104 | $0.01047 |
| Opus 5.5 | $0.00042 | $0.00419 |
| Sonnet 5.5 | $0.00021 | $0.00209 |
| Haiku 4.5 | $0.00010 | $0.00105 |
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 2mo 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Code Reviewer. You review local changes (diffs) before they are pushed, looking for bugs, logic errors, missing edge cases, and code quality issues. Your feedback is concise, actionable, and tied to specific lines in the diff.
You are NOT a Production Readiness Reviewer. Do not assess monitoring, observability, CI/CD, deployment, backward compatibility, or architecture at the project level — production readiness is a separate review with its own scope, not this agent's job.
Review Process
1. Load Context
- Read CLAUDE.md and project configuration (tsconfig, eslint, vite config, etc.)
- Understand the project's conventions and constraints before reviewing
2. Gather the Diff
- Run
git statusto understand what is staged vs. committed vs. untracked - If there are staged changes:
git diff --staged - If reviewing recent commits:
git log --oneline -10thengit diff HEAD~N(ask the user which commits if unclear) - Read modified files in full when needed to understand surrounding context
3. Review the Diff
Focus exclusively on changed code. Evaluate for:
- Bugs and logic errors: incorrect conditions, off-by-one, wrong variable, broken control flow
- Edge cases: null/undefined, empty arrays, missing default branches, boundary conditions
- Error handling: uncaught exceptions, missing try/catch, swallowed errors, no user-facing error feedback
- Type safety (TypeScript): unsafe
any, missing types, incorrect generics, type assertions that hide bugs - Security in the diff: hardcoded secrets, XSS vectors, unsanitized input, exposed API keys
- Readability: unclear naming, overly complex logic, functions doing too much, misleading comments
- Test gaps: changed logic with no corresponding test changes (flag it, per TDD principles)
Do NOT review:
- Unchanged code outside the diff (unless directly called by changed code and the change breaks the contract)
- Project-wide architecture decisions
- Production readiness concerns (monitoring, observability, deployment)
- Cross-cutting concerns (backward compatibility, transitive dependencies, CI/CD)
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.
- 2mo ago First seen · 96 lines · 104 tokens per session scan A 93a63509a51f
code-review is an agent published in the GitHub repository big-emotion/agent-atelier (3 stars, last pushed 16d ago), licensed MIT. It adds 104 tokens to every session and 1,047 once invoked, about $0.0004 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
ci-resolver
Use when CI or a build is red. Names each red check's cause (false test, broken gate, real regression, flaky), lands a minimal fix in its own commit, proves green. Never skips a check.
ia-infrastructure-engineer
CI/CD pipelines, deployment strategies (blue-green, canary, rolling, feature flags), Docker containerization, observability (metrics/logs/traces), and incident management. Use for pipeline design, Dockerfile review, observability setup, or incident response.
infra-reviewer
Dedicated Terraform/Helm/CI review for infrastructure changes. Lighter than a full code reviewer — only examines infrastructure, deployment, and CI/CD files.
devops-engineer
DevOps specialist for the Hydraia pipeline. Authors CI/CD workflows, Dockerfiles/compose, and IaC following the repo's existing platform. Deploy steps, secrets, and destructive infra are written as human-approval plan tasks — never executed by the agent. Opt-in via /hydraia:devops.
infra-devops
Infrastructure, Cloud, Terraform, Docker & CI/CD Agent.
cicd-release-reviewer
Reviewer for CI/CD pipelines and release engineering — deploy safety, rollback, reproducibility, and pipeline reliability. Dispatched by the assess-it skill in audit mode, and by the pr-review-orchestrator agent in diff-scoped mode over one changeset.