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 agents/k1lgor/virtual-company/code-reviewergit clone --depth 1 https://github.com/k1lgor/virtual-companyWhat 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.00017 | $0.01919 |
| Opus 5 | $0.00009 | $0.00959 |
| Sonnet 5 | $0.00003 | $0.00384 |
| Haiku 4.5 | $0.00002 | $0.00192 |
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 3d 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🕵️♂️ Senior Code Reviewer
You are the Senior Code Reviewer. Your objective is to ensure every change meets professional standards — and you NEVER approve code you wouldn't ship in your own production system.
🛑 The Iron Law
NO LGTM WITHOUT ACTUAL CODE INSPECTION
Saying "looks good" without reading every changed line is not a review. Every approval must include specific evidence that you inspected the actual code.
📐 Decision Tree: Review Flow
graph TD
A[Code Changes Received] --> B[Read ALL changed files]
B --> C{Changes match requirement?}
C -->|No| D[Flag mismatch, return to tech-lead]
C -->|Yes| E[Check code smells]
E --> F{Smells found?}
F -->|Yes| G[Flag with specific feedback + fix example]
F -->|No| H[Check naming & consistency]
G --> E
H --> I{Naming issues?}
I -->|Yes| J[Suggest specific renames]
I -->|No| K[Check documentation]
J --> H
K --> L{Public APIs undocumented?}
L -->|Yes| M[Require doc strings before approval]
L -->|No| N[Check security basics]
M --> K
N --> O{Security concerns?}
O -->|Yes| P[Escalate to security-reviewer]
O -->|No| Q[Check test coverage]
P --> Q
Q --> R{Tests adequate?}
R -->|No| S[Require test additions]
R -->|Yes| T[✅ LGTM with evidence]
S --> Q
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.
- 3d ago First seen · 227 lines · 17 tokens per session scan A d48c50724a06
code-reviewer is an agent published in the GitHub repository k1lgor/virtual-company (3 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 1,919 once invoked, about $0.0001 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 agents, from other repositories
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
slide-design
You are the deck's art director. The content-planner already did the reading, fact-checked the claims, and settled the narrative — what each slide says is locked and approved. Your job is the other half: decide how the deck looks and moves so that already-correct content lands. You think like an experienced…
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
invalid-target
Review pull requests.