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 billygit 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/billy)<a href="https://agentmods.dev/skills/lexfrei/ccc/billy"><img src="https://agentmods.dev/badge/skills/lexfrei/ccc/billy/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/billy"><img src="https://agentmods.dev/badge/skills/lexfrei/ccc/billy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 41 Skill grants unrestricted tool access without appropriate constraints. An agent with unfettered tool access can perform arbitrary actions including file modification, network requests, and code execution.Fix: Restrict tool access to only the tools required for the skill's stated purpose. Use an explicit allowlist rather than granting blanket access.
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.00000 | $0.00751 |
| Opus 5.5 | $0.00000 | $0.00300 |
| Sonnet 5.5 | $0.00000 | $0.00150 |
| Haiku 4.5 | $0.00000 | $0.00075 |
Grade A, and why
billy 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.
- **Network**: `curl` endpoints, check connectivity, DNS resolution, port availability How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Where's the proof, Billy? We need proof!
Someone made a claim. Stop everything and investigate. No proof — no trust.
Input
The argument is a claim that needs verification. Examples:
/billy "the runner is dead"/billy "this endpoint returns 500 on empty body"/billy "the migration broke prod"/billy "node memory is leaking"
Rules
- Do NOT take the claim at face value. Assume nothing. Verify everything.
- Do NOT stop at the first piece of evidence. Keep digging until you have a conclusive answer.
- Do NOT suggest — investigate. Run commands, read logs, check code, query APIs. Produce evidence.
- Do NOT fix anything. This is investigation only. Report findings, never apply changes.
Process
Launch an Agent (model: opus) to perform the investigation. The agent must:
Phase 1: Understand the claim
Parse the assertion. Identify:
- Subject: what system/component/process is involved
- Predicate: what is being claimed about it (dead, broken, leaking, failing, etc.)
- Implicit scope: timeframe, environment, context from the current conversation
Phase 2: Gather evidence
Use every available tool to collect evidence. Prioritize direct observation over inference:
- Processes and services:
ps,systemctl status,docker ps,kubectl get pods, health endpoints - Logs: application logs, system logs, journal, container logs,
dmesg - Code and config: read source code, check recent changes (
git log,git diff), review config files - Network:
curlendpoints, check connectivity, DNS resolution, port availability - Resources: disk space, memory, CPU, file descriptors, connection pools
- External systems: CI/CD status (
gh run list), monitoring dashboards, database state - History: git blame, recent deploys, recent config changes, cron jobs
Collect at least 3 independent pieces of evidence before forming a conclusion.
Phase 3: Attempt to reproduce
If the claim describes a failure or behavior:
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 · 97 lines · 0 tokens per session scan A 8c5a1c5f99de
billy is a skill published in the GitHub repository lexfrei/ccc (11 stars, last pushed 14d ago), licensed BSD-3-Clause. It costs nothing until one of its globs matches a file; then it loads 751 tokens. 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.