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 bengous/claude-code-plugins --skill issuegit clone --depth 1 https://github.com/bengous/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/bengous/claude-code-plugins/issue)<a href="https://agentmods.dev/skills/bengous/claude-code-plugins/issue"><img src="https://agentmods.dev/badge/skills/bengous/claude-code-plugins/issue.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.00060 | $0.00860 |
| Opus 5 | $0.00030 | $0.00430 |
| Sonnet 5 | $0.00012 | $0.00172 |
| Haiku 4.5 | $0.00006 | $0.00086 |
Grade A, and why
issue 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue
An issue is a prompt with context. Its reader is a different agent, in a fresh session, with no access to this conversation. The issue proves that the problem exists and where; it does not prescribe the solution. The reader plans.
Input
$ARGUMENTS
- Starts with a number: rewrite that issue. Fetch it with
gh issue view <n> --json title,body,labels,url, keep the facts that still hold, drop the rest. - Anything else: the request for a new issue.
- Empty: ask one question, "What is wrong, or what do you want?", then continue.
Ask nothing else unless the request cannot be located in the code at all.
Protocol
-
Project constraints. Read the repo's
AGENTS.mdorCLAUDE.mdfor two things only: the validation commands, and the boundaries the reader must respect. They go in Done when and Hints. -
Evidence. Locate the code the request touches. Read it before citing it. Each fact gets an anchor the reader can jump to:
path:lineplus the symbol name, or a commit hash. Rungit log --oneline -10 -- <file>when history explains the current state. Search once for a duplicate:gh issue list --search "<keywords>" --state all --limit 10; link a match in Evidence and say so to the user. -
Body. Fill the template below. Size follows the problem: a small bug fits in fifteen lines.
-
Confirm. Show the title and the full body. Ask one question: create (or update), or change something. Suggest labels only from
gh label list. -
Publish. Write the body to a temporary file outside the repo, then:
gh issue create --title "<title>" --body-file <tmp> --label "<a>,<b>" gh issue edit <n> --body-file <tmp>--body-filekeeps the markdown intact; inline--bodybreaks on backticks. Report the URL.
Template
## Problem
## Evidence
## Hints
## Done when
## Out of scope
Problem. What is observed and what is wanted, one to three sentences. No cause, no solution.
Evidence. One bullet per fact, each with its anchor. Quote the exact line when it is short. Include the reproduction command when one exists. Link related issues, PRs, and commits here; there is no separate "Related" section.
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.
- 4d ago First seen · 66 lines · 60 tokens per session scan A 074f6975ac01
issue is a skill published in the GitHub repository bengous/claude-code-plugins (4 stars, last pushed yesterday), licensed MIT. It adds 60 tokens to every session and 860 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
batch
Dispatch a night's batch of Todo tickets — one worktree and one pull request each — and leave a morning summary. Run explicitly; never inferred.
prep
Spec a ticket before it is dispatched. Brainstorms it, decides everything it can recommend an answer for, asks a present human about the little that survives, and leaves the spec, the decisions and anything still open as one ticket comment. No worktree, no branch, no pull request, and the ticket stays where it was.
work
Dispatch a tracker ticket into an isolated worktree and drive it autonomously to an open pull request, then stop for review. Pass interactive to brainstorm the ticket with a human before planning it. Use when asked to work a ticket end-to-end.
daily-working
End-to-end pipeline: pull a task from Redmine by ID, sanity-check and impact-assess it against the codebase before touching anything, implement it with the Claude CLI, verify the result in a real browser via the Claude Chrome extension (claude-in-chrome), and keep the Redmine ticket in sync throughout (in-progress…
release
Verify, sweep docs, cut a version — then hand the release sequence back.
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.