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/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/ariadoss/superskills/claude-md"><img src="https://agentmods.dev/badge/instructions/ariadoss/superskills/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.02713 | $0.02713 |
| Opus 5.5 | $0.01085 | $0.01085 |
| Sonnet 5.5 | $0.00543 | $0.00543 |
| Haiku 4.5 | $0.00271 | $0.00271 |
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 9d 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 — 184 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
VERSION gets one reviewed bump per merged change, never one per intermediate
commit: bump it when a change is about to land on main (on the feature
branch, at /ship time), re-reading latest main first so parallel branches
never claim the same number. The full decision model (SemVer vs CalVer vs
build IDs, release tags, changelog fragments for parallel agents) lives in
DEVELOPER_WORKFLOW.md:
- 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, .cursor-plugin/plugin.json, .cursor-plugin/marketplace.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.
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.
- 9d ago Changed · +5 lines · +116 tokens per session 26df9ee43bcb
- 15d ago Changed · +16 lines · +209 tokens per session d6d06b1e99d0
- 17d ago Changed · +5 lines · +92 tokens per session 9fdc5cff8f74
- 20d ago Changed · +23 lines · +283 tokens per session 57200bb5cc6a
- 25d ago Changed · +19 lines · +238 tokens per session 01ccae55a1de
- 1mo ago Changed · +21 lines · +352 tokens per session 6af58a8c8e70
- 1mo ago Changed · +18 lines · +203 tokens per session 53e3c0a2c997
- 1mo 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 (12 stars, last pushed 2d ago), licensed MIT. It adds 2,713 tokens to every session, about $0.0109 per session on Opus 5.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
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.