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 skills add abhinav503/flutter-agentic --skill review-codegit clone --depth 1 https://github.com/abhinav503/flutter-agenticWrote 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/abhinav503/flutter-agentic/review-code)<a href="https://agentmods.dev/skills/abhinav503/flutter-agentic/review-code"><img src="https://agentmods.dev/badge/skills/abhinav503/flutter-agentic/review-code/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/abhinav503/flutter-agentic/review-code"><img src="https://agentmods.dev/badge/skills/abhinav503/flutter-agentic/review-code.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00084 |
| Opus 5.5 | $0.00000 | $0.00034 |
| Sonnet 5.5 | $0.00000 | $0.00017 |
| Haiku 4.5 | $0.00000 | $0.00008 |
Grade A, and why
review-code 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 1mo 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
review-code
Run after any AI-generated code to catch rule violations before committing. Read the project rules, then audit the files the user just generated or modified.
If no files were specified, ask: "Which files or feature should I review?"
Then follow every check in the guide below and report a ✅/❌ checklist. Offer to fix each violation after reporting.
@docs/how-to/review-code.md
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.
- 1mo ago First seen · 12 lines · 0 tokens per session scan A 9ac221068248
review-code is a skill published in the GitHub repository abhinav503/flutter-agentic (10 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 84 tokens. 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 skills, from other repositories
develop-code-quality
Language-neutral code-quality rules for writing and reviewing code in any language - naming by intent, removing needless indirection, when to extract, safe direct assignment, redundant work, magic values, dead code and unread state, single source of truth, explicit tie-breaks, and code comments. Load together with the…
develop-code-spacing
Vertical spacing (blank lines) in code - how blank lines partition functions, tests, classes and modules into role-based paragraphs - plus a safe procedure for a spacing pass across many files or a whole repository with parallel agents. Load when writing or reviewing code layout, when code reads as one unbroken block…
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
new-skill
Scaffold a new brooks-lint analysis skill so it passes npm run validate and npm run evals on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends…
brooks-audit
Architecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books. Triggers when: user asks to audit architecture, review folder/module structure, check for circular imports, understand how the codebase is organized…
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…