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 ankur-gaurav161418/omniforge --skill requesting-code-reviewgit clone --depth 1 https://github.com/ankur-gaurav161418/omniforgeWrote 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/ankur-gaurav161418/omniforge/requesting-code-review)<a href="https://agentmods.dev/skills/ankur-gaurav161418/omniforge/requesting-code-review"><img src="https://agentmods.dev/badge/skills/ankur-gaurav161418/omniforge/requesting-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/ankur-gaurav161418/omniforge/requesting-code-review"><img src="https://agentmods.dev/badge/skills/ankur-gaurav161418/omniforge/requesting-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.00019 | $0.00069 |
| Opus 5.5 | $0.00008 | $0.00028 |
| Sonnet 5.5 | $0.00004 | $0.00014 |
| Haiku 4.5 | $0.00002 | $0.00007 |
Grade A, and why
Requesting 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
Requesting Code Review Skill
Generate clear code review summaries detailing architectural changes, risk assessments, and test coverage.
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 · 10 lines · 19 tokens per session scan A a6720873802a
Requesting Code Review is a skill published in the GitHub repository ankur-gaurav161418/omniforge (0 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 69 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-31.
Other skills, from other repositories
code-review-excellence
Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.
multi-reviewer-patterns
Coordinate parallel code reviews across multiple quality dimensions with finding deduplication, severity calibration, and consolidated reporting. Use this skill when organizing multi-reviewer code reviews, calibrating finding severity, or consolidating review results.
coderabbit-review
Use when you need to evaluate CodeRabbit PR comments and fix or reply.
doc-gather
Use when you need to gather context for a Jira ticket or PR. Resolves ticket metadata, clones relevant repos, collects candidate files, runs filtering pipeline, and produces workspace/context-package.json.
doc-review
Use this skill to perform adversarial review of AsciiDoc documentation against context sources. Checks factual accuracy, completeness, consistency, and hallucination. Produces workspace/review-findings.json.
addressing-review-feedback
How to work a task returned with review, QA or UAT findings. Use when a task is in needrevision or PR review comments are in your context.