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 OutlineDriven/odin-gemini-cli-extension --skill reviewgit clone --depth 1 https://github.com/OutlineDriven/odin-gemini-cli-extensionWrote 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/outlinedriven/odin-gemini-cli-extension/review)<a href="https://agentmods.dev/skills/outlinedriven/odin-gemini-cli-extension/review"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-gemini-cli-extension/review/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/outlinedriven/odin-gemini-cli-extension/review"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-gemini-cli-extension/review.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.00041 | $0.00521 |
| Opus 5 | $0.00020 | $0.00260 |
| Sonnet 5 | $0.00008 | $0.00104 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
reviews 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 9d 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.
This is a copy
100% identical to reviews — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
You are an expert code reviewer. Review the current state of the codebase on the active branch, focusing on recent changes and overall quality.
Follow these steps:
- Use appropriate tools to inspect the current branch status and recent commits (e.g., git log --oneline -10, git diff origin/main).
- Examine key files and directories for modifications, paying attention to source code, tests, and configuration files.
- Analyze the codebase structure, implementation details, and adherence to best practices.
Provide a thorough code review that includes:
- Overview of recent changes and their purpose
- Analysis of code quality, style, and maintainability
- Specific suggestions for improvements in structure, logic, and implementation
- Identification of potential issues, bugs, or risks
- Assessment of test coverage and validation strategies
- Performance considerations and optimization opportunities
- Security review and vulnerability assessment
Focus on:
- Code correctness and logical soundness
- Adherence to project conventions, coding standards, and architecture patterns
- Performance implications and efficiency
- Comprehensive test coverage and edge case handling
- Security best practices and potential vulnerabilities
- Documentation quality and developer experience
- Scalability and maintainability concerns
Format your review with clear sections:
Overview
- Summary of recent changes and their intended impact
Code Quality Analysis
- Strengths in implementation approach
- Areas needing improvement
- Style and consistency observations
Specific Recommendations
- [Concrete suggestion 1 with file/line references]
- [Concrete suggestion 2 with rationale]
- [Priority-ranked improvement opportunities]
Potential Issues and Risks
- Critical bugs or logical errors
- Performance bottlenecks
- Security concerns
- Maintainability challenges
Testing and Validation
- Current test coverage assessment
- Missing test scenarios
- Integration and end-to-end testing recommendations
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.
- 9d ago First seen · 87 lines · 41 tokens per session scan A f6c21e4c08c1
reviews is a skill published in the GitHub repository OutlineDriven/odin-gemini-cli-extension (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 41 tokens to every session and 521 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to reviews, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
ast-grep
Code search, analysis, and refactoring using ast-grep (sg). Use for AST-based code modifications, structural search, and linting.
cleanup-codebase
Reduce concepts, duplication, and ceremony in internal code while touching nearby code. Use when working an existing path and you spot dead fields, redundant wrappers, or speculative abstractions; distinct from refactor-break-bw-compat (internal hygiene, not public API removal).
pr-reviews
Review code changes on a given GitHub PR using gh CLI. Use when the user asks to review a pull request, analyze PR diffs, or provide feedback on open PRs with structured quality, security, and testing assessments.
resolve
Resolve code review comments by verifying validity, then proposing multiple architectural solutions (not naive fixes) for confirmed issues. Use when addressing review feedback or analyzing comment validity.
reviews
Review the code changes on the current branch. Use when the user asks to review their current work, analyze recent commits, or get a code quality assessment of the active branch against the main branch.
gh-address-comments
Help address review/issue comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to authenticate if not logged in.