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 agentmods add instructions/phucbm/skills/claude-mdgit clone --depth 1 https://github.com/phucbm/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/instructions/phucbm/skills/claude-md)<a href="https://agentmods.dev/instructions/phucbm/skills/claude-md"><img src="https://agentmods.dev/badge/instructions/phucbm/skills/claude-md.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 | $0.00385 | $0.00385 |
| Opus 5 | $0.00192 | $0.00192 |
| Sonnet 5 | $0.00077 | $0.00077 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
skills 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 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 26 lines · 385 tokens per session scan A fe456d35347a
skills CLAUDE.md is an instructions file published in the GitHub repository phucbm/skills (2 stars, last pushed 2mo ago), with no licence file. It adds 385 tokens to every session, about $0.0019 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 instructions, from other repositories
platform-skills copilot-instructions.md
Copilot instructions for nitinjain999/platform-skills, covering platform engineering instructions for github copilot, version: 1.40.0, source: https://github.com/nitinjain999/platform-skills, response contract and core principles.
recursive-decomposition-skill AGENTS.md
Instructions for massimodeluisa/recursive-decomposition-skill, covering agents: recursive-decomposition skill, read these first (mandatory), language policy, non-negotiables and commands.
stockbit-mcp CLAUDE.md
Claude Code instructions for INo-xious/stockbit-mcp, covering claude.md, what this is, commands, the map and three invariants. do not break them; each has a test.
curie CLAUDE.md
Claude Code instructions for curie-eng/curie, covering one entry point: curie, release train selection and architecture decision records (adrs).
embedded-systems-architect AGENTS.md
Instructions for Zachariah9420/embedded-systems-architect: This repository ships an agent skill for embedded-systems and edge-AI development work.
agentic-validation-skills CLAUDE.md
Claude Code instructions for vivekkrishna/agentic-validation-skills, covering agentic test automation guidelines (cige), 1. establish context before testing, 2. anchor every test to intent, 3. define guardrails before executing and 4. treat execution as adaptive guidance.