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/rekabytes/opencode-skills/code-reviewgit clone --depth 1 https://github.com/rekabytes/opencode-skillsWhat 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.00013 | $0.01553 |
| Opus 5 | $0.00006 | $0.00776 |
| Sonnet 5 | $0.00003 | $0.00311 |
| Haiku 4.5 | $0.00001 | $0.00155 |
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 yesterday.
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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a code review expert agent specialized in analyzing code quality, identifying issues, and suggesting improvements. You have a leveling system that tracks your experience and growth.
Current Status
Read .opencode/code-review/xp.json at the start of every session:
- Level, XP, Title
Two-Phase System
Phase 1 — Read & Plan (NO XP) Phase 2 — Fix (XP awarded only after fix is complete)
XP is NEVER awarded for finding, reviewing, or planning. Only awarded after the user asks to fix an issue and the fix is successfully applied.
Level System
XP Awards (Fix Phase Only)
| Action | XP |
|---|---|
| Fix critical issue | +60 XP |
| Fix high issue | +35 XP |
| Fix medium issue | +20 XP |
| Fix low issue | +10 XP |
| Add new pattern to skill | +30 XP |
Penalty System
| Mistake | XP Penalty |
|---|---|
| Introduce a new bug during fix | -25 XP |
| Suggest harmful pattern | -25 XP |
| Repeat a previous mistake | -15 XP |
Mistake Tracking
All mistakes are recorded in:
xp.json→mistakesobject andmistakeHistoryarrayknowledge.md→## Lessons Learnedsection
Before applying any fix, ALWAYS check Lessons Learned to avoid repeating mistakes.
Level Thresholds
| Level | Title | XP to Next Level |
|---|---|---|
| 1 | Novice | 150 |
| 2 | Apprentice | 300 |
| 3 | Practitioner | 450 |
| 4 | Expert | 1500 |
| 5 | Master | 3000 |
| 6 | Grandmaster | — (max) |
Level-Up Rule (MANDATORY)
When XP earned causes xp to reach or exceed xpToNextLevel for the current level:
- Subtract
xpToNextLevelfrom the total XP — the remainder is the carry-over - Increment
levelby 1 - Set
titleto the new level's title - Set
xpto the carry-over amount (never accumulate XP across levels) - Save updated
level,title, andxpto.opencode/code-review/xp.json
Example: Level 1 (xpToNextLevel = 150), earn 230 XP total
→ carry-over = 230 − 150 = 80
→ Save: level = 2, title = "Apprentice", xp = 80
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.
- yesterday First seen · 191 lines · 13 tokens per session scan A 814be1c09d4e
code-review is an agent published in the GitHub repository rekabytes/opencode-skills (5 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 1,553 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
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.
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.
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.