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 agentmods add skills/new1direction/korgex/requesting-code-reviewnpx skills add New1Direction/korgex --skill requesting-code-reviewgit clone --depth 1 https://github.com/New1Direction/korgexWhat 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 | $0.00019 | $0.00279 |
| Opus 5 | $0.00010 | $0.00139 |
| Sonnet 5 | $0.00004 | $0.00056 |
| Haiku 4.5 | $0.00002 | $0.00028 |
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 2d 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
You are biased toward your own work — you test what you built, not what's required. A fresh-eyes pass catches what you can't see. Do this before finalizing anything non-trivial.
- Prepare the change. Make sure it's coherent:
git diffis clean, tests pass. - Dispatch a reviewer with NO prior context. Spawn a subagent (the
Agenttool) and give it ONLY: the diff, the original requirement, and the instruction to review for correctness, edge cases, security, missing tests, and clarity — and to try to REFUTE that the change is correct. Don't tell it your conclusions. - For high-stakes work, use more than one reviewer with different lenses (correctness / security / does-it-actually-meet-the-requirement). Majority skepticism wins.
- Act on the findings. Fix real issues. If you disagree, verify with code, not assertion. Distinguish blockers from nits.
- Re-verify after fixes (see verify-before-done), then report what review found and what you changed.
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.
- 2d ago First seen · 23 lines · 19 tokens per session scan A 07670bb7fdce
requesting-code-review is a skill published in the GitHub repository New1Direction/korgex (5 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 279 once invoked, about $0.0001 per session on Opus 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
vibe-ui-design
Use when designing UI/UX, defining design systems, choosing color palettes, typography, spacing, or component primitives. Triggers on "design system", "design tokens", "color palette", "UI 设计", "深色工业风", "design language".
vibe-security
Use when performing security audits, vulnerability scanning, dependency checks, or secure code reviews. Triggers on "security audit", "scan vulnerabilities", "安全审查", "漏洞扫描", "OWASP", "dependency check".
vibe-ui-beautify
Use when adding animations, micro-interactions, 3D effects, glassmorphism, or "juicy" tactile feedback to UI components. Triggers on "animation", "hover effect", "transition", "动效", "果汁感", "Framer Motion", "GSAP", "3D 视效".
vibe-plan
Use this skill to create a phased development plan based on requirements, architecture, and API docs.
vibe-test
Use when writing tests, performing unit testing, integration testing, or verifying system functionality. Triggers on "write tests", "run tests", "add unit test", "TDD", "测试", "跑测试".
vibe-autopilot
Use this skill when the user requests fully autonomous, 24/7 hands-free development without human intervention.