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/addxai/enterprise-harness-engineering/code-reviewnpx skills add addxai/enterprise-harness-engineering --skill code-reviewgit clone --depth 1 https://github.com/addxai/enterprise-harness-engineeringWrote 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/addxai/enterprise-harness-engineering/code-review)<a href="https://agentmods.dev/skills/addxai/enterprise-harness-engineering/code-review"><img src="https://agentmods.dev/badge/skills/addxai/enterprise-harness-engineering/code-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.00089 | $0.05966 |
| Opus 5 | $0.00044 | $0.02983 |
| Sonnet 5 | $0.00018 | $0.01193 |
| Haiku 4.5 | $0.00009 | $0.00597 |
Grade A, and why
code-review scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s --request POST --header "PRIVATE-TOKEN: $GITLAB_TOKEN" \ How it starts
The opening of the file, as written. The whole thing — 518 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
Reviews code changes across three dimensions per /architect standards: document compliance, content quality, and end-to-end consistency.
Each review step uses a multi-role parallel, multi-round iterative review mechanism to ensure depth and thoroughness.
Core principles:
- Documents exist, code doesn't → Allowed (design-first)
- Code exists, documents don't → Fail (undocumented implementation)
Execution Flow
Step 0: Collect change scope → Get the diff, classify by file type
Step 1: Document compliance check → Check against /architect format rules item by item (multi-role parallel, minimum 3 rounds)
Step 2: Content quality review → Understand the content, evaluate against /architect quality standards (multi-role parallel, minimum 3 rounds)
Step 3: End-to-end consistency → Trace User Story ↔ design ↔ code ↔ tests ↔ observability (multi-role parallel, minimum 3 rounds)
Step 4: Summary and scoring → Aggregate all round results, red-line determination + improvement suggestions + pass/fail
Hard requirement: Steps 1-3 must have at least 3 rounds of review. Marking
Review completein Round 1 or Round 2 and moving to the next step is not allowed. Round 3 is the final confirmation round, ensuring all findings are thorough and free of false positives.
Step 0: Collect Change Scope
Auto-detect the change source and uniformly obtain the diff:
| Trigger Scenario | How to Obtain | Example |
|---|---|---|
| Remote MR | GitLab API GET /projects/{id}/merge_requests/{iid}/changes + commits |
review MR !52 |
| Local committed | git diff main..HEAD or git diff HEAD~N |
review recent commits |
| Local uncommitted | git diff + git diff --staged |
review my changes |
After obtaining the diff, classify by file type to determine review dimensions:
| Category | File Pattern | Review Dimensions |
|---|---|---|
| Product docs | docs/product/** |
Step 1 + Step 2 (User Story format and quality) |
| Architecture docs | docs/architecture/** |
Step 1 + Step 2 (design quality) + Step 3 |
| Testing docs | docs/testing/** |
Step 1 + Step 2 (test completeness) + Step 3 |
| Observability docs | **/observability.md |
Step 2 (observability coverage) + Step 3 |
| Feature code | server/**, app/**, etc. |
Step 2 (code quality) + Step 3 |
| Test code | **/*_test.* |
Step 2 (test quality) + Step 3 |
| Deployment config | k8s/**, .gitlab-ci.yml |
Step 2 (configuration correctness) |
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 · 518 lines · 89 tokens per session scan A fa5c9d07e2ca
code-review is a skill published in the GitHub repository addxai/enterprise-harness-engineering (44 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 89 tokens to every session and 5,966 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
peon-ping-create-pack
Internal — invoked headlessly by peon create; humans should run peon create instead. Author and render a brand-new PeonPing draft pack — invoked headlessly as: "Use the peon-ping-create-pack skill to draft a pack: name= flavor= vibe= draftroot= . Follow the skill exactly." Authors all 7 CESP categories honoring the…
peon-ping-config
Update peon-ping configuration — volume, pack rotation, categories, active pack, and other settings. Use when user wants to change peon-ping settings like volume, enable round-robin, add packs to rotation, toggle sound categories, or adjust any config.
peon-ping-use
Set which voice pack (character voice) plays for the current chat session. Automatically enables sessionoverride rotation mode if not already set. Use when user wants a specific character voice like GLaDOS, Peon, or Kerrigan for this conversation.
peon-ping-rename
Rename the current Claude session for peon-ping notifications and terminal tab title. Use when user wants to give this session a custom name like "/peon-ping-rename Auth Refactor". Call with no argument to reset to auto-detect.
peon-ping-toggle
Toggle peon-ping sound notifications on/off. Use when user wants to mute, unmute, pause, or resume peon sounds during a Claude Code session. Also handles config changes like volume, pack rotation, categories — any peon-ping setting.
peon-ping-log
Log exercise reps for the Peon Trainer. Use when user says they did pushups, squats, or wants to log reps. Examples - "/peon-ping-log 25 pushups", "/peon-ping-log 30 squats", "log 50 pushups".