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 d-gangz/dgang-skills --skill claude-mdgit clone --depth 1 https://github.com/d-gangz/dgang-skillsWrote 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/d-gangz/dgang-skills/claude-md)<a href="https://agentmods.dev/skills/d-gangz/dgang-skills/claude-md"><img src="https://agentmods.dev/badge/skills/d-gangz/dgang-skills/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/skills/d-gangz/dgang-skills/claude-md"><img src="https://agentmods.dev/badge/skills/d-gangz/dgang-skills/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.00019 | $0.01714 |
| Opus 5 | $0.00010 | $0.00857 |
| Sonnet 5 | $0.00004 | $0.00343 |
| Haiku 4.5 | $0.00002 | $0.00171 |
Grade A, and why
claude-md 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 12d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create or Improve a CLAUDE.md
Goal
CLAUDE.md is the only content guaranteed to appear in every Agent conversation in a repo — and the repo may hold code, business docs, a knowledge base, or any mix. Every line it carries is paid on every task, so it must carry only rules that are universally applicable (defined below) — that test drives every decision here. Such files usually land under ~100 lines, but length itself is not a rule: a longer file is fine when every line passes the test. Treat growth past that mark only as a cue to re-check the rules against it.
Process
- Know the repo. If you're creating from scratch, or the edit relies on repo knowledge you haven't verified, read
references/explore.mdand do the exploration first. - Map the domain docs. Inspect existing
CONTEXT.md,CONTEXT-MAP.md,PEOPLE.md, ADRs, andagent-docs/domain.md. Establish whether the repo is code or non-code: non-code means the deliverable is documents, knowledge, or operations rather than software — supporting scripts don't change this. Use multi-context only whenCONTEXT-MAP.mdexists or the repo has verified distinct domain contexts; code layout or monorepo structure alone is not evidence. Otherwise use single-context. - Edit or create. If a CLAUDE.md exists, make targeted edits and steer the file toward the template below — don't rewrite from scratch unless it's fundamentally broken. If none exists, write one following the template.
- Write the domain consumer guide. Read
references/domain.md, then create or updateagent-docs/domain.mdfrom that seed using the verified layout. Do not create emptyCONTEXT.md,CONTEXT-MAP.md, or ADR files. - Disclose the rest. Material that is only sometimes applicable goes in
agent-docs/, not the root CLAUDE.md. - Validate the whole file against the checklist.
Universally applicable
A rule belongs in CLAUDE.md only if it applies to every single task in the repo: would it apply when fixing a bug? Adding a feature? Drafting a document? Doing research? If the answer is "only sometimes", it belongs in a disclosure target or nowhere.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 105 lines · 19 tokens per session scan A 980240f2e559
claude-md is a skill published in the GitHub repository d-gangz/dgang-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 1,714 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…