Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/alteredcraft/claude-code-plugins/claude-mdgit clone --depth 1 https://github.com/AlteredCraft/claude-code-pluginsWhat 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 | $0.01184 | $0.01184 |
| Opus 5 | $0.00592 | $0.00592 |
| Sonnet 5 | $0.00237 | $0.00237 |
| Haiku 4.5 | $0.00118 | $0.00118 |
Grade A, and why
claude-code-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 2d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AlteredCraft Plugin Marketplace
IMPORTANT: Prior to any implementation, always review the Claude Marketplace Reference: https://code.claude.com/docs/en/plugin-marketplaces.md
Naming Convention
Plugin names
All plugins use the ac-<topic> pattern to avoid namespace collisions:
| Directory | Plugin Name | Example Invocation |
|---|---|---|
artifact-workflow/ |
ac-artifact-workflow |
/ac-artifact-workflow:build |
ideation/ |
ac-ideation |
/ac-ideation:dev-product-brainstorm |
dev-tools/ |
ac-dev-tools |
/ac-dev-tools:journal |
document-gen/ |
ac-document-gen |
/ac-document-gen:powerpoint |
anchored-interview/ |
ac-anchored-interview |
/ac-anchored-interview:create-skill |
Directory names don't need the prefix—only the name field in plugin.json.
Keep each plugin as its own namespace; don't collapse multiple plugins into a single global namespace. Per-plugin namespaces preserve install granularity and keep each plugin's topic visible in the slash command.
Skill names
Skills live inside a plugin namespace, so the slash command already carries the plugin's topic. Keep skill names short and action-oriented — don't repeat the plugin's noun in the skill name.
- Verb-first.
create-skill,draft-essay,build,journal. Reads as an action. - Don't repeat the plugin topic. Inside
ac-anchored-interview, the skill iscreate-skill, notcreate-anchored-interview-skill. The namespace already says "anchored interview." - Avoid noun-first phrasings like
skill-creatororessay-creator— they read like job titles rather than actions.
Good: /ac-anchored-interview:create-skill · /ac-document-gen:powerpoint · /ac-dev-tools:journal
Avoid: /ac-anchored-interview:create-anchored-interview-skill · /ac-anchored-interview:anchored-interview-skill-creator
Plugin Directory Structure
Each plugin follows this structure:
plugins/<plugin-dir>/
├── .claude-plugin/
│ └── plugin.json # Required: plugin metadata
├── README.md # Required: documentation
├── skills/ # Optional: reusable skills
│ └── <skill-name>/
│ ├── SKILL.md # Required for each skill
│ ├── scripts/ # Optional: executable scripts
│ ├── references/ # Optional: reference docs
│ └── resources/ # Optional: templates, assets
└── commands/ # Optional: slash commands
└── <command-name>.md
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.
- 2d ago First seen · 127 lines · 1,184 tokens per session scan A e3d3fe2d3b2a
claude-code-plugins CLAUDE.md is an instructions file published in the GitHub repository AlteredCraft/claude-code-plugins (13 stars, last pushed 3mo ago), licensed MIT. It adds 1,184 tokens to every session, about $0.0059 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-30.
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.
buildNext
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
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, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit 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.
langchain 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.