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 kivo360/OmoiOS --skill code-reviewgit clone --depth 1 https://github.com/kivo360/OmoiOSWrote 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/kivo360/omoios/code-review)<a href="https://agentmods.dev/skills/kivo360/omoios/code-review"><img src="https://agentmods.dev/badge/skills/kivo360/omoios/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/kivo360/omoios/code-review"><img src="https://agentmods.dev/badge/skills/kivo360/omoios/code-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.00013 | $0.01114 |
| Opus 5.5 | $0.00005 | $0.00446 |
| Sonnet 5.5 | $0.00003 | $0.00223 |
| Haiku 4.5 | $0.00001 | $0.00111 |
Grade A, and why
code-review scanned grade A with 2 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
fetch(userProvidedUrl); // BAD Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
os.system(f"ls {user_input}") # BAD How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
Perform thorough code reviews using this structured approach.
Review Checklist
1. Security (CRITICAL)
- Injection vulnerabilities: SQL, command, XSS, template injection
- Authentication: Proper auth checks, secure session handling
- Authorization: Access control on all sensitive operations
- Secrets: No hardcoded credentials, API keys, tokens
- Input validation: All user input validated and sanitized
- Output encoding: Proper encoding for context (HTML, URL, JS)
2. Logic & Correctness
- Requirements met: Code implements what was specified
- Edge cases: Null/empty/boundary conditions handled
- Error handling: Exceptions caught and handled appropriately
- Race conditions: Concurrent access handled correctly
- State management: State transitions are valid
3. Performance
- N+1 queries: Database queries in loops
- Memory leaks: Unclosed resources, retained references
- Unnecessary computation: Repeated calculations, missing caching
- Blocking operations: Async operations not blocking main thread
- Large payloads: Response sizes reasonable
4. Maintainability
- Single responsibility: Each function/class has one purpose
- DRY: No duplicated code
- Naming: Clear, descriptive names for variables/functions
- Comments: Complex logic explained, not obvious code
- Type hints: Types annotated (Python/TypeScript)
5. Testing
- Test coverage: New code has tests
- Test quality: Tests verify behavior, not implementation
- Edge case tests: Boundary conditions tested
- Integration tests: System interactions tested
Review Output Format
## Code Review: {file/component}
### Summary
{1-2 sentence overall assessment}
### 🔴 Critical Issues
{Must fix before merge}
#### Issue 1: {Title}
- **Location**: `file.py:42`
- **Problem**: {Description}
- **Impact**: {Security/correctness impact}
- **Fix**: {Suggested solution}
### 🟡 Suggestions
{Should consider fixing}
#### Suggestion 1: {Title}
- **Location**: `file.py:88`
- **Current**: {What it does now}
- **Suggested**: {Better approach}
- **Reason**: {Why this is better}
### 🟢 Positive Notes
{Good patterns to highlight}
- Good use of {pattern} at `file.py:100`
- Clear error handling in {function}
### Verdict
- [ ] ✅ Approve
- [ ] 🔄 Request Changes
- [ ] 💬 Needs Discussion
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 · 155 lines · 13 tokens per session scan A aa533df55092
code-review is a skill published in the GitHub repository kivo360/OmoiOS (81 stars, last pushed 14d ago), licensed Apache-2.0. It adds 13 tokens to every session and 1,114 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 2 findings (makes network calls, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
pr-review
Review open PRs two ways - default is a per-PR deep review with severity-tagged findings, inline comments, and a verdict; --survey runs a risk-tiered triage digest of what's safe to merge first.
pr-triage
First-touch triage for external pull requests - verdict, label, and a welcoming comment within minutes of open.
feedback-builder
Point Aeon at a service's /feedback endpoint - pull what agents reported (bugs, missing features), triage and cluster it, then build the best accepted request as a PR for a human to approve.
[REPLACE: SKILL_NAME]
First-touch review of newly opened PRs on [REPLACE: WATCHEDREPO] — verdict + welcoming comment + label.
code-review
Systematic code review for bugs, security, style, and performance.
creating-pr
Creates GitHub Pull Requests with existing PR detection, branch pushing, and intelligent title/body generation. Use when user requests to create pull request, open PR, update PR, push for review, ready for review, send for review, get this reviewed, make a PR, share code, request review, create draft PR, submit for…