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 kngwyc3/Agent-Learning-Hub --skill my-skillgit clone --depth 1 https://github.com/kngwyc3/Agent-Learning-HubWrote 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/kngwyc3/agent-learning-hub/my-skill)<a href="https://agentmods.dev/skills/kngwyc3/agent-learning-hub/my-skill"><img src="https://agentmods.dev/badge/skills/kngwyc3/agent-learning-hub/my-skill/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/kngwyc3/agent-learning-hub/my-skill"><img src="https://agentmods.dev/badge/skills/kngwyc3/agent-learning-hub/my-skill.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.00027 | $0.00437 |
| Opus 5 | $0.00014 | $0.00218 |
| Sonnet 5 | $0.00005 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
code-review-risk-check 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 10d 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 Risk Check
Use this skill to turn a raw code diff into a concise engineering review. The goal is not to summarize every changed file; the goal is to find the issues that could break users, production, security, data integrity, or future maintenance.
When To Use
- The user asks for a code review, PR review, diff review, or regression risk review.
- The input contains changed files, a patch, commit diff, or PR context.
- The expected output is a review comment or a list of findings.
When Not To Use
- The user asks for implementation rather than review.
- There is no code, diff, or behavioral description to inspect.
- The request is only about formatting, naming, or style preferences.
Inputs
- Code diff or file list.
- User intent, issue, PR description, or acceptance criteria if available.
- Test output, linter output, or CI failures if available.
Steps
- Identify the user-facing behavior or contract touched by the change.
- Scan the diff for correctness risks first: control flow, data shape, state transitions, error handling, permissions, concurrency, and persistence.
- Check whether tests cover the riskiest changed behavior.
- Ignore low-signal style issues unless they hide a real bug.
- Report findings first, ordered by severity.
- If no issues are found, say so clearly and mention remaining test gaps or residual risk.
Output
Use templates/review_report.md as the output shape:
- Findings first.
- Each finding must include severity, file or symbol, impact, and a concrete fix direction.
- Summary is optional and must stay short.
Verification
Before returning the review:
- At least one finding has concrete evidence, or the report explicitly says no findings.
- No fabricated file paths or line numbers.
- No broad rewrite suggestions unless the current diff requires them.
- Test gaps are tied to changed behavior, not generic advice.
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- samples/bad_report.md 198 B
- samples/good_report.md 659 B
- scripts/smoke_check.py 845 B runs code
- templates/eval-skill/SKILL.md 1.4 KB
- templates/eval-skill/tests/smoke.md 153 B
- templates/lark-skill/SKILL.md 1.3 KB
- templates/lark-skill/tests/smoke.md 117 B
- templates/minimal-skill/SKILL.md 393 B
- templates/minimal-skill/tests/smoke.md 106 B
- templates/review_report.md 497 B
- tests/smoke.md 787 B
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.
- 10d ago First seen · 53 lines · 27 tokens per session scan A 9efadabcef56
code-review-risk-check is a skill published in the GitHub repository kngwyc3/Agent-Learning-Hub (128 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 437 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-30.
Other skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…