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 FlorianBruniaux/claude-code-plugins --skill prgit clone --depth 1 https://github.com/FlorianBruniaux/claude-code-pluginsWrote 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/florianbruniaux/claude-code-plugins/pr)<a href="https://agentmods.dev/skills/florianbruniaux/claude-code-plugins/pr"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-plugins/pr/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/florianbruniaux/claude-code-plugins/pr"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-plugins/pr.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.00016 | $0.01542 |
| Opus 5.5 | $0.00006 | $0.00617 |
| Sonnet 5.5 | $0.00003 | $0.00308 |
| Haiku 4.5 | $0.00002 | $0.00154 |
Grade A, and why
pr 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create pull request
Analyze changes, detect scope issues, and create a well-structured PR following project conventions.
Process
- Analyze Changes: Calculate complexity score from files, commits, and directories
- Detect Scope Issues: Warn if PR is too large or mixes unrelated changes
- Suggest Split: If needed, group commits by scope and propose separate PRs
- Collect Info: Ask for type, target branch, draft status, labels
- Generate Content: Create TLDR + description + checklist
- Create PR: Execute
gh pr createwith proper formatting - Remind Follow-up: Display post-PR checklist (SonarQube, Claude Review)
Complexity score
Calculate PR complexity to detect if split is needed:
| Criterion | Weight | Description |
|---|---|---|
| Code files | x2 | *.ts, *.tsx (excluding tests) |
| Test files | x0.5 | *.test.ts, *.spec.ts |
| Config files | x1 | *.json, *.yml, *.md |
| Directories | x3 | Distinct src/* directories |
| Commits | x1 | Number of commits |
Thresholds: 0-15 ✅ Normal | 16-25 ⚠️ Large | 26+ 🔴 Split recommended
Scope coherence
| Pattern | Verdict |
|---|---|
| Single scope | ✅ OK |
| Related scopes (sessions + calendar) | ✅ OK |
| Unrelated scopes (payments + auth) | 🔴 Split |
| feat + fix same scope | ✅ OK |
| feat + fix different scopes | 🔴 Split |
Split suggestion format
When split is recommended, display:
🔴 Scope trop large (score: 32)
Commits par scope :
├── payments (5 commits, 8 fichiers)
│ ├── feat(payments): add Stripe checkout
│ └── fix(payments): handle currency
│
└── notifications (3 commits, 6 fichiers)
└── feat(notifications): add email templates
💡 Suggestion :
1. PR #1 : feature/payments-stripe → Commits payments
2. PR #2 : feature/notifications → Commits notifications
Options :
[A] Continuer avec une seule PR (non recommandé)
[B] Découper (semi-auto - commandes git fournies)
[C] Voir détail fichiers
Semi-auto split provides copy-paste commands:
git checkout develop
git checkout -b feature/payments-stripe
git cherry-pick abc1234 def5678
git push -u origin feature/payments-stripe
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.
- yesterday First seen · 205 lines · 16 tokens per session scan A dea9d22e49ca
pr is a skill published in the GitHub repository FlorianBruniaux/claude-code-plugins (43 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 1,542 once invoked, about $0.0001 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-10-29.
Other skills, from other repositories
trace-scan
Trace scan (§4.1/§4.2): before a commit, scans the staged changes and the message for AI traces (co-author trailers, footers, robot emoji, tool names) and vendor template names. The git hooks apply it automatically.
sc-diff-report
Incremental security scan for changed files only — optimized for PR and commit-level reviews.
feature-publish
Commit the feature, write the PR body, publish in the selected mode, and drive the PR.
pr-review
Review open PRs two ways - default is a per-PR deep review with severity-tagged findings, inline comments, and a verdict; --survey runs a risk-tiered triage digest of what's safe to merge first.
pr-triage
First-touch triage for external pull requests - verdict, label, and a welcoming comment within minutes of open.
feedback-builder
Point Aeon at a service's /feedback endpoint - pull what agents reported (bugs, missing features), triage and cluster it, then build the best accepted request as a PR for a human to approve.