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 Geeksfino/openskills --skill code-reviewgit clone --depth 1 https://github.com/Geeksfino/openskillsWrote 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/geeksfino/openskills/code-review)<a href="https://agentmods.dev/skills/geeksfino/openskills/code-review"><img src="https://agentmods.dev/badge/skills/geeksfino/openskills/code-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/geeksfino/openskills/code-review"><img src="https://agentmods.dev/badge/skills/geeksfino/openskills/code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.00303 |
| Opus 5.5 | $0.00012 | $0.00121 |
| Sonnet 5.5 | $0.00006 | $0.00061 |
| Haiku 4.5 | $0.00003 | $0.00030 |
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 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
Code Review Skill
Perform thorough code reviews following this methodology.
Review Checklist
1. Correctness
- Does the code do what it's supposed to do?
- Are there any logic errors?
- Are edge cases handled?
2. Security
- Input validation and sanitization
- Authentication and authorization
- Sensitive data handling
- SQL injection, XSS, and other vulnerabilities
3. Performance
- Algorithm complexity
- Unnecessary computations
- Memory leaks or inefficient memory usage
- Database query optimization
4. Maintainability
- Code readability and clarity
- Appropriate naming conventions
- Single responsibility principle
- DRY (Don't Repeat Yourself)
5. Testing
- Test coverage
- Edge case testing
- Integration tests where appropriate
Output Format
Structure your review as:
## Summary
[One paragraph overview]
## Critical Issues
[Must fix before merge]
## Suggestions
[Nice to have improvements]
## Positive Observations
[What's done well]
Guidelines
- Be constructive, not critical
- Explain why something is an issue
- Suggest specific fixes when possible
- Acknowledge good patterns and practices
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 · 67 lines · 29 tokens per session scan A d18d57ff6d8b
code-review is a skill published in the GitHub repository Geeksfino/openskills (71 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 29 tokens to every session and 303 once invoked, about $0.0001 per session on Opus 5.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
security-specialist
Runs security audits on codebases — full scans, diff reviews, threat models, vulnerability triage, remediation guidance, and finding tracking. Activate when the user says "security scan", "audit this repo", "review this PR for security", "threat model", "triage vulnerabilities", "fix this vuln", or "track findings".
agent-plugin-eval
Audit, score, and compare repositories containing portable Agent Plugins against the official Agent Plugins specification. Use when asked to review a plugin repo, check plugin.json or mcp.json conformance, assess bundled skills and MCP servers, produce an evidence-cited 0–100 plugin scorecard, identify release…
review
Review an openEHR specification document for quality, completeness, and convention compliance in specifications-XX repos. This skill should be used when the user asks to review, lint, or quality-check an openEHR spec or chapter, validate its conventions, or run a pre-release review. Not for prose-style advice (use…
auditing-skills
Use when checking this repository's skills for security or quality issues before sharing them, or remediating findings across skills.
lsp-investigate
Investigate code using LSP tools. Register a project, then use definitions, references, call hierarchies, type hierarchies, hover, and diagnostics to understand code structure, trace bugs, and assess change impact.
code-standards
Language-agnostic code standards for writing clean, maintainable code. Covers modular design, functional patterns, error handling, security, and testing. Make sure to use this skill whenever writing, refactoring, or reviewing any code, even for quick fixes, prototypes, or single-file changes. This is the baseline for…