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 rhawk117/agentmaster --skill agentmaster-reviewgit clone --depth 1 https://github.com/rhawk117/agentmasterWrote 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/rhawk117/agentmaster/agentmaster-review)<a href="https://agentmods.dev/skills/rhawk117/agentmaster/agentmaster-review"><img src="https://agentmods.dev/badge/skills/rhawk117/agentmaster/agentmaster-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/rhawk117/agentmaster/agentmaster-review"><img src="https://agentmods.dev/badge/skills/rhawk117/agentmaster/agentmaster-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.00074 | $0.00189 |
| Opus 5.5 | $0.00030 | $0.00076 |
| Sonnet 5.5 | $0.00015 | $0.00038 |
| Haiku 4.5 | $0.00007 | $0.00019 |
Grade A, and why
agentmaster-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
This skill is a router. The review runs inside the agentmaster-review
custom agent, which carries the frontier model pin and dispatches scout and
code-analyst workers for all evidence.
Invoke the agentmaster-review custom agent now, passing the diff range or
scope verbatim. Do not review inline in this session. If the custom agent is
not available, tell the user to run python install.py install --target copilot from the
agentmaster bundle.
Scope under review: $ARGUMENTS
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 · 16 lines · 74 tokens per session scan A c410e217bddd
agentmaster-review is a skill published in the GitHub repository rhawk117/agentmaster (1 stars, last pushed 3mo ago), licensed MIT. It adds 74 tokens to every session and 189 once invoked, about $0.0003 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
gaia-issue-resolver
End-to-end plan → implement → review pipeline that takes one triaged Gaia issue to a merged-ready PR, with Kill Criteria on the issue and zero follow-up debt. Use when someone says: "resolve this issue", "take #N end-to-end", "work the P0 queue", "fix and ship this issue", "run the resolver", "close out this issue…
senior-engineer
Use when reviewing code for architecture, quality, or correctness; making technical design decisions; evaluating trade-offs between approaches; refactoring complex systems; mentoring on engineering practices; writing technical design documents; or any task requiring deep technical judgement across the full stack.
kotlin-reviewer
Use when reviewing a Kotlin/Spring Boot pull request, systematic checklist covering architecture, idioms, testing, security, and observability.
frontend-reviewer
Use when reviewing a frontend pull request or diff, auditing a frontend repo for gaps, or checking whether code has drifted from the project's documented conventions.
review-board
Generate a single-file HTML "story-paced" walkthrough of a finished feature for human code review. Use after completing a feature or merging a PR — produces docs/review/ .html with sidebar nav, Why/Tradeoff/Deferred callouts, status pills, and a reviewer's checklist.
loop-council
Sends an open design question to several independent voices in parallel and returns a decision with its evidence. Use before building anything that touches money, permissions, auth, or schema, or whenever the honest answer is "I am not sure".