Borrowing it
Nothing to install: this file belongs to ariadoss/superskills. 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/ariadoss/superskills/main/CLAUDE.mdgit clone --depth 1 https://github.com/ariadoss/superskillsWrote 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/ariadoss/superskills/claude-md)<a href="https://agentmods.dev/instructions/ariadoss/superskills/claude-md"><img src="https://agentmods.dev/badge/instructions/ariadoss/superskills/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.01220 | $0.01220 |
| Opus 5 | $0.00610 | $0.00610 |
| Sonnet 5 | $0.00244 | $0.00244 |
| Haiku 4.5 | $0.00122 | $0.00122 |
Grade A, and why
superskills 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 7d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Superskills
Engineering standards (applies to all code in this repo)
All code here — setup, scripts/, skill helpers, anything executable — follows
ENGINEERING_STANDARDS.md: TDD, DRY, SOLID, YAGNI,
to a Google/Meta-quality bar. Concretely:
- Shell/library code is tested with
bats. Run./tests/run.shbefore committing any change tosetup,scripts/, ortests/. New behavior gets a failing test first (TDD); logic shared across call sites lives in one place (scripts/lib/skills-lib.sh), not copy-pasted (DRY). - Skills that generate or review code must enforce the same bar by
referencing
ENGINEERING_STANDARDS.md, not by restating it. When you add or edit a code-producing or quality-gate skill, point it at that file.
Versioning
Always increment VERSION before committing and pushing any change:
- Patch (2.x.X) — bug fixes, typo corrections, small clarifications to existing skills
- Minor (2.X.0) — new skills, significant updates to existing skills, new tool support
- Major (X.0.0) — breaking changes, major new capability bundles
Update the version badge in README.md to match (e.g. v2.1.0 → v2.2.0).
After bumping VERSION, run ./scripts/sync-version.sh to propagate it into the
plugin manifests (.claude-plugin/plugin.json, .claude-plugin/marketplace.json,
.codex-plugin/plugin.json). These version fields are what trigger the native
"plugins updated" alert in Claude Code and Codex — a bump that doesn't reach them
means existing plugin installs never see the update. VERSION is the single source
of truth; the manifests are generated from it, never hand-edited.
Always re-run ./setup after a pull or after adding a skill
Skills are exposed to the tools as symlinks created by ./setup. Edits to an
existing skill propagate instantly (the symlink points at the live file),
but a new skill is invisible until ./setup runs again to create its link.
So:
- After every
git pullin this repo — run./setup(apost-mergegit hook does this automatically once you've run setup once; if you cloned fresh, run it manually the first time). - After adding a new skill locally, before you push — run
./setupso the new skill is linked and testable in your own environment.
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.
- 7d ago First seen · 77 lines · 1,220 tokens per session scan A 25209cadeccf
superskills CLAUDE.md is an instructions file published in the GitHub repository ariadoss/superskills (9 stars, last pushed yesterday), licensed MIT. It adds 1,220 tokens to every session, about $0.0061 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
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).
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.
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 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).
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.