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/miaoy0ushan/fp/review-changesnpx skills add MiaoY0uShan/FP --skill review-changesgit clone --depth 1 https://github.com/MiaoY0uShan/FPWrote 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/miaoy0ushan/fp/review-changes)<a href="https://agentmods.dev/skills/miaoy0ushan/fp/review-changes"><img src="https://agentmods.dev/badge/skills/miaoy0ushan/fp/review-changes.svg" alt="Measured on agentmods" 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.00014 | $0.00242 |
| Opus 5 | $0.00007 | $0.00121 |
| Sonnet 5 | $0.00003 | $0.00048 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
review-changes 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 6d 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.
This is a copy
100% identical to review-changes — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Review Changes
Perform a thorough, risk-aware code review using the knowledge graph.
Steps
- Run
detect_changes_toolto get risk-scored change analysis. - Run
get_affected_flows_toolto find impacted execution paths. - For each high-risk function, run
query_graph_toolwith pattern="tests_for" to check test coverage. - Run
get_impact_radius_toolto understand the blast radius. - For any untested changes, suggest specific test cases.
Output Format
Provide findings grouped by risk level (high/medium/low) with:
- What changed and why it matters
- Test coverage status
- Suggested improvements
- Overall merge recommendation
Token Efficiency Rules
- ALWAYS start with
get_minimal_context(task="<your task>")before any other graph tool. - Use
detail_level="minimal"on all calls. Only escalate to "standard" when minimal is insufficient. - Target: complete any review/debug/refactor task in ≤5 tool calls and ≤800 total output tokens.
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.
- 6d ago First seen · 30 lines · 14 tokens per session scan A 2fa19140eb35
review-changes is a skill published in the GitHub repository MiaoY0uShan/FP (3 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 242 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to review-changes, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
html-ppt-zhangzara-block-frame
Rescuing a messy startup deck into a board-grade system — the diagnosis, the page grammar, and the rebuilt proof pages. Built as a decision-grade design craft deck for founders, exec presenter.
build-test
Run the project's build / typecheck / lint / test commands and emit the build.passing + tests.passing signals devloop convergence reads.
patch-edit
Apply one rewrite-plan step at a time as small reviewable file edits, never rewriting whole files when a localised change suffices.
doca-flow
Build and debug DOCA Flow applications on supported NVIDIA NICs/DPUs: define match/action pipes, initialize ports and representors, choose forwarding targets, validate pipes before hardware programming, read counters, match the Flow version to the installed DOCA release, and diagnose Flow API errors. Trigger on DOCA…
dynamo-interconnect-check
Validate that a Dynamo deployment's NIXL/UCX/NCCL interconnect is ready for disaggregated serving over RDMA/NVLink. Use after recipe-runner brings a deployment up (especially disagg/multi-node) to confirm the KV transport is correct; use troubleshoot for diagnosing already-failed pods.
mcore-create-issue
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.