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 breaking-brake/cc-wf-studio --skill pr-review-analysisgit clone --depth 1 https://github.com/breaking-brake/cc-wf-studioWrote 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/breaking-brake/cc-wf-studio/pr-review-analysis)<a href="https://agentmods.dev/skills/breaking-brake/cc-wf-studio/pr-review-analysis"><img src="https://agentmods.dev/badge/skills/breaking-brake/cc-wf-studio/pr-review-analysis/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/breaking-brake/cc-wf-studio/pr-review-analysis"><img src="https://agentmods.dev/badge/skills/breaking-brake/cc-wf-studio/pr-review-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00072 | $0.01099 |
| Opus 5 | $0.00036 | $0.00549 |
| Sonnet 5 | $0.00014 | $0.00220 |
| Haiku 4.5 | $0.00007 | $0.00110 |
Grade A, and why
pr-review-analysis 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 92 lines · 72 tokens per session scan A cc4dad675e6e
pr-review-analysis is a skill published in the GitHub repository breaking-brake/cc-wf-studio (5,375 stars, last pushed yesterday), with no licence file. It adds 72 tokens to every session and 1,099 once invoked, about $0.0004 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
logic-component-shape
Decision tree for single component versus container/presenter, which componentStructure to generate, and which componentType to declare. Invoked by logic-placement and logic-review, not directly.
logic-placement
Decide where new logic belongs — component shape, logic layer, and store variant — when designing a component, service, or store in an Angular/Otter workspace. Use logic-review to assess existing code.
logic-review
Review existing components, services, or stores for misplaced logic — presenter leaks, componentType mismatches, wrong store variants. Use logic-placement when designing something new.
logic-state-layer
Decision tree for whether logic belongs in the component class, a service, or an NgRx store, including service scope and where API calls go. Invoked by logic-placement and logic-review, not directly.
logic-store-type
Decision tree for which NgRx store variant to generate — entity or simple, sync or async. Invoked by logic-placement and logic-review once a store is justified, not directly; it does not decide whether a store is warranted.
a11y-axe-playwright
Write and review automated axe accessibility scans using @axe-core/playwright: setup, tag selection, selector scoping, interpreting violations, and waiving known rules.