Borrowing it
Nothing to install: this file belongs to tt-a1i/matt-skills-with-to-goal. 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/tt-a1i/matt-skills-with-to-goal/main/CLAUDE.mdgit clone --depth 1 https://github.com/tt-a1i/matt-skills-with-to-goalWrote 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/tt-a1i/matt-skills-with-to-goal/claude-md)<a href="https://agentmods.dev/instructions/tt-a1i/matt-skills-with-to-goal/claude-md"><img src="https://agentmods.dev/badge/instructions/tt-a1i/matt-skills-with-to-goal/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/tt-a1i/matt-skills-with-to-goal/claude-md"><img src="https://agentmods.dev/badge/instructions/tt-a1i/matt-skills-with-to-goal/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.00977 | $0.00977 |
| Opus 5.5 | $0.00391 | $0.00391 |
| Sonnet 5.5 | $0.00195 | $0.00195 |
| Haiku 4.5 | $0.00098 | $0.00098 |
Grade A, and why
matt-skills-with-to-goal 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 yesterday.
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 — 29 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skills are organized into bucket folders under skills/:
engineering/: daily code workproductivity/: daily non-code workflow toolsmisc/: kept around but rarely used, not promotedin-progress/: beta: public on purpose, feedback wanted, not shipped in the plugindeprecated/: historical source excluded from default distribution; old human docs live underdocs/archived/
Every skill in engineering/ or productivity/ (the promoted buckets) must have a reference in the top-level README.md and an entry in .claude-plugin/plugin.json's skills array (the Claude Code plugin ships exactly the promoted set). Skills in misc/, in-progress/, and deprecated/ must not appear in either.
Install commands are copied verbatim from .agents/install-block.md. .claude-plugin/marketplace.json makes this fork its own single-plugin marketplace. Run claude plugin validate . --strict after touching either manifest. The upstream managed-install evidence and this fork's distinct installation routes live in .agents/adr/0002-ship-as-a-claude-code-plugin.md.
Each skill entry in the top-level README.md must link the skill name to its SKILL.md.
Each bucket folder has a README.md that lists every skill in the bucket with a one-line description, with the skill name linked to its SKILL.md. The promoted buckets' README.mds and the top-level README.md group entries into User-invoked and Model-invoked; non-promoted bucket README.mds (misc/, in-progress/) use a flat list.
Skills in engineering/ and productivity/ also have a human-facing docs page at docs/<bucket>/<skill-name>.md (the docs tree mirrors those two bucket folders under skills/). The published URL is https://aihero.dev/skills-<skill-name> regardless of bucket: the docs path is repo organisation only. When you add, rename, or change the behaviour of a skill in engineering/ or productivity/, create or re-sync its docs page following .agents/writing-docs.md. A finished page carries four sections: What it does, When to reach for it, Common questions, and It's working if. writing-docs.md holds the template, the section order, and where to hunt for the questions. Skills in the non-promoted buckets (misc/, in-progress/, deprecated/) get no docs page.
Every SKILL.md is either user-invoked (disable-model-invocation: true plus policy.allow_implicit_invocation: false in agents/openai.yaml, reachable only by the human) or model-invoked (model- or user-reachable). See .agents/invocation.md.
To (re)link every skill outside deprecated/ and misc/ into the local harness skill directories (~/.claude/skills, ~/.agents/skills), run scripts/link-skills.sh. Each entry is a symlink into this repo, so a git pull keeps installed skills current; re-run the script after adding, removing, or renaming a skill.
Rejected directions get archived, not merely decided. When this fork turns down a skill direction or a design — its own calls, not only upstream feature requests — record it in .out-of-scope/ under the convention triage already follows (skills/engineering/triage/OUT-OF-SCOPE.md): one file per concept, kebab-case concept name. The reason must be durable — scope, mechanism, or cost, never a temporary circumstance, because a decision resting on the current moment is a deferral rather than a rejection. Never record something that was in fact built; a false rejection poisons the concept matching that makes the directory worth reading.
Before syncing upstream, publishing to origin, or refreshing local installs, read docs/maintaining-fork.md. It covers review merges, bounded diff inspection, skill/doc consistency, and validation before publication.
Use plain punctuation in repository prose, consistent with upstream: rewrite sentences with commas, colons, periods, parentheses, or conjunctions.
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.
- yesterday Changed · -1 lines · -88 tokens per session c0fc4b3a8c5e
- 17d ago Changed · +2 lines · +26 tokens per session 04bd69b12532
- 1mo ago Changed · +2 lines · +50 tokens per session 31458f5876d8
- 1mo ago First seen · 26 lines · 989 tokens per session scan A 0adf517395f7
matt-skills-with-to-goal CLAUDE.md is an instructions file published in the GitHub repository tt-a1i/matt-skills-with-to-goal (189 stars, last pushed 2d ago), licensed MIT. It adds 977 tokens to every session, about $0.0039 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-30.
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).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.