Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/huskar20/huskar20-plugins/claude-md)<a href="https://agentmods.dev/instructions/huskar20/huskar20-plugins/claude-md"><img src="https://agentmods.dev/badge/instructions/huskar20/huskar20-plugins/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.01479 | $0.01479 |
| Opus 5 | $0.00740 | $0.00740 |
| Sonnet 5 | $0.00296 | $0.00296 |
| Haiku 4.5 | $0.00148 | $0.00148 |
Grade A, and why
huskar20-plugins 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 5d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — rules for authoring plugins in this marketplace
This file governs every plugin in this repository. It is loaded automatically when developing here with Claude. Human contributors: read it too — CI enforces the structural parts, and reviewers enforce the rest.
What this repo is
A plugin marketplace: a Git repo whose .claude-plugin/marketplace.json lists
plugins that users install into Claude. Each plugin lives in its own directory
under plugins/. Adding a plugin means adding its directory and registering it
in marketplace.json.
Golden rules
-
One plugin, one directory under
plugins/<plugin-name>/.<plugin-name>is kebab-case (lowercase letters, numbers, hyphens) and must match thenamein that plugin'splugin.jsonand its entry inmarketplace.json. Names must not contain "claude" or "anthropic" — Claude Code rejects them as impersonating an official marketplace. (The GitHub repo name may contain "claude"; only thenamefields inside the manifests are checked.) -
Never commit personal data or secrets. No real names (beyond an author attribution the author consents to), emails, phone numbers, API keys, tokens, spreadsheet/document IDs, file paths outside the repo, or customer data. A plugin's users generate their own data locally at runtime — it must never land in this repo. CI scans for common leak patterns; do not defeat it.
One exception: a public template document ID that the plugin itself owns. A plugin may hardcode the ID of a Google Doc/Sheet it publishes as a starting template (view-only, link-shared, containing no user data) so setup can copy it in one call instead of rebuilding it through the browser. Such an ID must be documented in the plugin's README, and the template must contain nothing but empty structure. This exception covers only template IDs the marketplace publishes — a user's own spreadsheet ID never belongs in the repo.
-
Validate before every PR:
python3 scripts/validate.pymust pass. If you have the Claude CLI, also runclaude plugin validate plugins/<name>/.claude-plugin/plugin.json. -
Bump versions on every change. Update the plugin's
plugin.jsonversion(semver) AND the matchingversioninmarketplace.json. New plugins start at0.1.0.
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.
- 5d ago First seen · 136 lines · 1,479 tokens per session scan A 53570a8cb03f
huskar20-plugins CLAUDE.md is an instructions file published in the GitHub repository huskar20/huskar20-plugins (3 stars, last pushed 22d ago), licensed MIT. It adds 1,479 tokens to every session, about $0.0074 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
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).
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.
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 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.