Borrowing it
Nothing to install: this file belongs to FlorianBruniaux/cc-skill-usage. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/FlorianBruniaux/cc-skill-usage/main/CLAUDE.mdgit clone --depth 1 https://github.com/FlorianBruniaux/cc-skill-usageWrote 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/instructions/florianbruniaux/cc-skill-usage/claude-md)<a href="https://agentmods.dev/instructions/florianbruniaux/cc-skill-usage/claude-md"><img src="https://agentmods.dev/badge/instructions/florianbruniaux/cc-skill-usage/claude-md/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/instructions/florianbruniaux/cc-skill-usage/claude-md"><img src="https://agentmods.dev/badge/instructions/florianbruniaux/cc-skill-usage/claude-md.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.01606 | $0.01606 |
| Opus 5.5 | $0.00642 | $0.00642 |
| Sonnet 5.5 | $0.00321 | $0.00321 |
| Haiku 4.5 | $0.00161 | $0.00161 |
Grade A, and why
cc-skill-usage CLAUDE.md 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 2mo 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.
is one file you can `curl` and run. How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cc-skill-usage - Project Context
What this is
A single-file Python CLI. It reads Claude Code's own JSONL transcripts under
~/.claude/projects/ and reports Skill invocation analytics: counts, timing,
project breakdown, and the message that triggered each call. Retroactive by
design, it reads history already on disk instead of requiring a hook
installed ahead of time.
Repository layout
cc-skill-usage # the entire tool, one file, no package, no build step
README.md # usage reference for humans
EXAMPLES.md # goal-oriented scenarios mapped to the command that answers them
CHANGELOG.md # every fix/feature with the bug it addressed and the verification
llms.txt # compact index for LLM consumption (llmstxt.org format)
prompts/ # paste-into-a-session prompts. Two are about this tool (scenario
# smoke test, deep-dive report); project-reality-check.md is
# project-agnostic and works on any repo in any language
.claude/skills/ # skill-usage-report, a Skill that drives and interprets the CLI
LICENSE # MIT
Adding a doc file means updating three indexes, not one: the README link
list, llms.txt (its whole job is being the complete index), and the layout
block above. All three drifted once already when EXAMPLES.md and
prompts/ landed.
There is no src/, no test suite directory, no CI config. Keep it that way
unless a real need forces otherwise: the entire value of this tool is that it
is one file you can curl and run.
The one invariant that matters more than any feature
A Skill is invoked only when a transcript record's
message.content[] contains a block with type == "tool_use" and
name == "Skill". The skill name lives in input.skill. Nothing else counts,
not a mention in prose, not a file path, not a human typing the skill's name
in a sentence.
This was verified twice, independently, in the same session that built this
tool: once by the Python parser, once by a from-scratch grep '"name":"Skill"' | jq '.message.content[]? | select(...) | .input.skill' pipeline. Both
returned identical counts on the same data. If you touch the parsing logic in
cc-skill-usage, re-run that same cross-check before trusting a new number.
Do not assume a plausible-looking count is correct just because the code ran
without error.
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.
- 2mo ago First seen · 117 lines · 1,606 tokens per session scan A 0aaa2201669f
cc-skill-usage CLAUDE.md is an instructions file published in the GitHub repository FlorianBruniaux/cc-skill-usage (7 stars, last pushed 1mo ago), licensed MIT. It adds 1,606 tokens to every session, about $0.0064 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.