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/victordibia/designing-multiagent-systems/code-reviewnpx skills add victordibia/designing-multiagent-systems --skill code-reviewgit clone --depth 1 https://github.com/victordibia/designing-multiagent-systemsWhat 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.00014 | $0.00264 |
| Opus 5 | $0.00007 | $0.00132 |
| Sonnet 5 | $0.00003 | $0.00053 |
| Haiku 4.5 | $0.00001 | $0.00026 |
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 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.
What it actually says
Code Review Skill
Review Checklist
1. Correctness
- Does the code do what it claims?
- Are edge cases handled (null, empty, bounds)?
- Is error handling appropriate?
2. Security
- Input validation present?
- No SQL injection, XSS, command injection?
- Secrets not hardcoded?
- Permissions checked?
3. Performance
- No N+1 queries?
- Appropriate data structures?
- Unnecessary loops or allocations?
4. Maintainability
- Clear naming?
- Functions do one thing?
- No magic numbers?
- Tests included?
Review Format
For each issue found:
**[SEVERITY] file:line - Brief description**
Problem: What's wrong
Impact: Why it matters
Suggestion: How to fix
Severities: CRITICAL, HIGH, MEDIUM, LOW, NIT
Workflow
- Read the diff or changed files
- Understand the intent (PR description, commit messages)
- Check each file against the checklist
- Summarize findings with severity levels
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 · 53 lines · 14 tokens per session scan A 257aa72f98da
code-review is a skill published in the GitHub repository victordibia/designing-multiagent-systems (829 stars, last pushed 8d ago), licensed Apache-2.0. It adds 14 tokens to every session and 264 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-30.
Other skills, from other repositories
google-agents-cli-deploy
This skill should be used when the user wants to "deploy an agent", "deploy my ADK agent", "set up CI/CD", "configure secrets", "troubleshoot a deployment", or needs guidance on Agent Runtime, Cloud Run, or GKE deployment targets, or binding an agent to an Agent Gateway. Covers deployment workflows, service accounts…
google-agents-cli-eval
This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Agent Platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset…
google-agents-cli-workflow
This skill should be used when the user wants to "develop an agent", "build an agent using ADK", "run the agent locally", "debug agent code", "test an agent", "deploy an agent", "publish an agent", "monitor an agent", or needs the ADK (Agent Development Kit) development lifecycle and coding guidelines. Entrypoint for…
google-agents-cli-observability
This skill should be used when the user wants to "set up tracing", "monitor my agent", "configure logging", "add observability", "debug production traffic", or needs guidance on monitoring deployed agents, including ADK (Agent Development Kit) agents. Covers Cloud Trace, prompt-response logging, BigQuery Agent…
google-agents-cli-publish
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini Enterprise", "publish to Gemini Enterprise", or needs guidance on the agents-cli publish gemini-enterprise command. Also use when the user wants to "manage agents in Agent Registry"…
google-agents-cli-scaffold
This skill should be used when the user wants to "create an agent project", "start a new ADK project", "build me a new agent", "add CI/CD to my project", "add deployment", "enhance my project", or "upgrade my project". Part of the agents-cli skills suite. Covers agents-cli scaffold create, scaffold enhance, and…