Borrowing it
Nothing to install: this file belongs to luongnv89/skills. 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/luongnv89/skills/main/CLAUDE.mdgit clone --depth 1 https://github.com/luongnv89/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/luongnv89/skills/claude-md)<a href="https://agentmods.dev/instructions/luongnv89/skills/claude-md"><img src="https://agentmods.dev/badge/instructions/luongnv89/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.1 | $0.01133 | $0.01133 |
| Opus 5 | $0.00566 | $0.00566 |
| Sonnet 5 | $0.00227 | $0.00227 |
| Haiku 4.5 | $0.00113 | $0.00113 |
Grade C, and why
skills CLAUDE.md scanned grade C 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 6d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Ask before destructive ops (`rm -rf`, `git reset --hard`, force-push, branch delete). How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — Agent Skills Catalog
Project context for Claude when working in this repo. Skill definitions live here; the runtime that loads them lives in ~/.claude/skills/ (out of scope for edits).
Critical commands
- Validate a skill:
python3 ~/.claude/skills/skill-creator/scripts/quick_validate.py skills/<skill-name> - Package a skill:
python3 ~/.claude/skills/skill-creator/scripts/package_skill.py skills/<skill-name> - Scaffold a new skill:
python3 ~/.claude/skills/skill-creator/scripts/init_skill.py <name> --path skills/ - Local install dry-run:
bash install.sh(interactive TUI; never pipe to non-tty without flags)
There is no npm, pnpm, make, or pytest in this repo. Don't invent test commands.
Architecture map
skills/<name>/SKILL.md— required skill definition with YAML frontmatter (name,description,metadata.version,metadata.author).skills/<name>/references/— on-demand docs the agent loads when the skill triggers.skills/<name>/scripts/— executable helpers shipped with the skill.skills/<name>/agents/— subagent prompts.skills/<name>/docs/README.md— human-only catalog page; must start with the AI-skip HTML comment.install.sh/remote-install.sh— end-user installers (bash, no deps).dist/— generated.skillbundles. Never edit by hand.*-workspace/— scratch dirs for individual skills. Never commit working files there.- Root
*.mdfiles (CHANGELOG, CONTRIBUTING, etc.) — repo-level governance, not skill content.
Hard rules
- IMPORTANT: Bump
metadata.version(semver) on every SKILL.md edit. No exceptions. - IMPORTANT: Quote any frontmatter string containing
:#-<>|,&?!to keep YAML valid. - YOU MUST keep each
SKILL.mdunder 500 lines. Split overflow intoreferences/. - YOU MUST start every
docs/README.mdwith the AI-skip HTML comment (see existing skills for the boilerplate). - Never edit anything under
~/.claude/skills/or~/.claude/CLAUDE.mdfrom this repo. - Never edit
dist/artifacts; regenerate viapackage_skill.pyinstead. - Never commit
*-workspace/contents,.claude/scheduled_tasks.lock, or local scratch files. - Never commit secrets,
.env, or anything matching**/credentials*. - NEVER add
Co-Authored-By: Claudeto any commit message. - Do not commit or push without an explicit user request — drafting the message is fine, executing isn't.
- Use Conventional Commits (
feat:,fix:,chore:,docs:). Breaking changes go in the body, not the title. - Skill
namefield must exactly match the parent directory name (lowercase, hyphens, no consecutive hyphens). - Do not rewrite a whole SKILL.md for a one-line change. Use targeted edits.
- When a skill mutates a git repo, its SKILL.md must contain a "Repo Sync Before Edits" section.
- Run
quick_validate.pyagainst any skill you touched before declaring done.
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.
- 6d ago First seen · 68 lines · 1,133 tokens per session scan C 21faf0b0dad1
skills CLAUDE.md is an instructions file published in the GitHub repository luongnv89/skills (123 stars, last pushed yesterday), licensed MIT. It adds 1,133 tokens to every session, about $0.0057 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.