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 staruhub/CrewClaw --skill pr-summary-writergit clone --depth 1 https://github.com/staruhub/CrewClawWrote 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/staruhub/crewclaw/pr-summary-writer)<a href="https://agentmods.dev/skills/staruhub/crewclaw/pr-summary-writer"><img src="https://agentmods.dev/badge/skills/staruhub/crewclaw/pr-summary-writer/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/staruhub/crewclaw/pr-summary-writer"><img src="https://agentmods.dev/badge/skills/staruhub/crewclaw/pr-summary-writer.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.00189 |
| Opus 5 | $0.00010 | $0.00095 |
| Sonnet 5 | $0.00004 | $0.00038 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
pr-summary-writer 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 9d 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
PR Summary Writer
Overview
Write a short summary that helps reviewers and stakeholders understand a change.
When to Use
Use after reading a PR, local diff, or review notes.
Workflow
- State what changed.
- State why it changed.
- List verification evidence.
- Name remaining risks.
- Keep the tone factual.
Common Pitfalls
- Do not turn uncertainty into certainty.
- Do not omit failed checks.
- Do not include implementation trivia unless it affects risk.
Verification Checklist
- Summary is understandable without reading every file.
- Risks and failed checks are visible.
- No unsupported claims are included.
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.
- 9d ago First seen · 38 lines · 19 tokens per session scan A e9bbb8457174
pr-summary-writer is a skill published in the GitHub repository staruhub/CrewClaw (22 stars, last pushed 3d ago), licensed Apache-2.0. It adds 19 tokens to every session and 189 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
cross-review
Verify an implementer's diff with an INDEPENDENT, different-vendor sub-agent (diff plus contract only); turn blocking issues into fix-tasks and loop until clean.
security-audit
Security audit expert for OWASP Top 10, CVE analysis, code review, and penetration testing methodology.
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
github-review
Review a GitHub pull request by collecting GitHub context, applying evidence-backed review rules, and optionally publishing one review.
spawn-reviewers
Spawn and collect the reviewer fleet at stage20spawnreviewers. Consumes spawn.json.spec (the authoritative spawn spec from derive-spawn-spec / derive-static-spec), resolves GRAPHPROJECT, builds per-agent prompts from the per-agent template + role suffixes (Bug Hunter A/B, Unified Auditor, Domain Critics, Impact…
code-review
Review a set of code changes using evidence-backed findings, explicit confidence, and a clear coverage summary.