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 lexfrei/ccc --skill patch-statusgit clone --depth 1 https://github.com/lexfrei/cccWrote 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/lexfrei/ccc/patch-status)<a href="https://agentmods.dev/skills/lexfrei/ccc/patch-status"><img src="https://agentmods.dev/badge/skills/lexfrei/ccc/patch-status/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/lexfrei/ccc/patch-status"><img src="https://agentmods.dev/badge/skills/lexfrei/ccc/patch-status.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.00100 | $0.00907 |
| Opus 5.5 | $0.00040 | $0.00363 |
| Sonnet 5.5 | $0.00020 | $0.00181 |
| Haiku 4.5 | $0.00010 | $0.00091 |
Grade A, and why
patch-status scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl --silent "https://patchwork.kernel.org/api/1.2/patches/?project=netdevbpf&msgid=<message-id>" | jq '.[0] | {state, delegate: .delegate.username, web: .web_url}' How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Patchwork tracks what maintainers will do with a patch; the mailing list tracks what people said about it. Check both before concluding anything: a thread with zero replies can still be accepted, and a thread full of praise can sit at changes-requested.
Query by Message-ID
curl --silent "https://patchwork.kernel.org/api/1.2/patches/?project=netdevbpf&msgid=<message-id>" | jq '.[0] | {state, delegate: .delegate.username, web: .web_url}'
<message-id>is bare, without angle brackets — the ID of a patch mail (1/N,2/N, ...). Cover letters are not patches; querying a0/NID returns an empty list.project=netdevbpfcovers netdev and bpf. Other kernel subsystems have their own project slugs on the same instance — list them viahttps://patchwork.kernel.org/api/1.2/projects/and match bylist_email. Some subsystems do not use patchwork at all; an empty result for every patch of a series means look at the thread and the maintainer's git tree instead.- Other projects run their own instances with the same API (U-Boot lives on
patchwork.ozlabs.org,project=uboot).
What the states mean
| state | meaning | your move |
|---|---|---|
new |
in the queue, nobody triaged it | wait |
under-review |
a maintainer is looking | wait |
changes-requested |
review asked for changes | answer every comment in-thread, then new version as a new thread |
superseded |
a newer version of the series replaced it | check the newest version instead |
accepted / queued |
applied to the maintainer tree | done; netdev also sends an "applied" mail to the thread |
rejected / not-applicable |
will not be taken as-is | read the thread for the reason before doing anything |
deferred / awaiting-upstream |
parked on something external | find what it waits for in the thread |
delegate set to a maintainer (e.g. netdev) means the series is in that queue — a good sign, not a request for action.
A reply in the thread reading pw-bot: cr (or pw-bot: changes-requested) is a bot command that moved the series to changes-requested. Treat it exactly like the state: the next posting is a new version in a new thread, never a reply with fixed patches.
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 · 45 lines · 100 tokens per session scan A c42e4d07b1e6
patch-status is a skill published in the GitHub repository lexfrei/ccc (11 stars, last pushed 14d ago), licensed BSD-3-Clause. It adds 100 tokens to every session and 907 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.