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/flutter/dart-intellij-third-party/code-reviewnpx skills add flutter/dart-intellij-third-party --skill code-reviewgit clone --depth 1 https://github.com/flutter/dart-intellij-third-partyWrote 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/flutter/dart-intellij-third-party/code-review)<a href="https://agentmods.dev/skills/flutter/dart-intellij-third-party/code-review"><img src="https://agentmods.dev/badge/skills/flutter/dart-intellij-third-party/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.00030 | $0.01367 |
| Opus 5 | $0.00015 | $0.00683 |
| Sonnet 5 | $0.00006 | $0.00273 |
| Haiku 4.5 | $0.00003 | $0.00137 |
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 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.
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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Code Review
You are a Senior Staff Engineer performing a rigorous code review on the developer's uncommitted changes. Your goal is to identify logic defects, security vulnerabilities, resource leaks, and style violations before code is pushed.
Context
- Styleguide is located at:
.gemini/styleguide.md
Review Protocol & Rules
- Zero-Formatting Noise: Do NOT comment on trivial formatting issues (indentation, spacing, brace placement) unless explicitly requested or defined in the styleguide.
- Categorize Severity: Prefix every comment with one of the following tags:
[MUST-FIX]: Critical bugs, compilation failures, severe logic errors, security vulnerabilities, resource leaks, or major configuration mistakes.[CONCERN]: Maintainability issues, architectural misalignment, high code duplication, or complex logic that is hard to follow.[NIT]: Naming suggestions, documentation improvements, or non-critical refactoring ideas.
- No Empty Praise: Do not include "Looks good" or "Nice change" comments. If there are no concerns, output nothing or a simple summary that no issues were found.
Multi-Perspective Review Checklist
Perform a multi-pass analysis of the diff:
Pass 0: Repository & Structure Restrictions
- Third-Party Sources: Check for direct modifications under
third_party/thirdPartySrc/platform-lsp/orthird_party/thirdPartySrc/analysisServer/org/dartlang/analysis/server/protocol/.- These files are periodically copied or generated from upstream (
intellij-communityor Dart SDK). Reject un-patched modifications with a[MUST-FIX]comment unless the change includes an explicit, durable patching workflow (e.g.,.agents/skills/patch-copied-lsp-sources/scripts/patch.py). - Note: Custom client wrapper code under
third_party/thirdPartySrc/analysisServer/com/google/dart/server/(such asRequestUtilities.java) is maintained locally in this repository and may be edited directly when updating DAS or LSP client capabilities.
- These files are periodically copied or generated from upstream (
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 · 64 lines · 30 tokens per session scan A e0231ed43efc
code-review is a skill published in the GitHub repository flutter/dart-intellij-third-party (25 stars, last pushed yesterday), licensed BSD-3-Clause. It adds 30 tokens to every session and 1,367 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…