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/cozystack/ccp/claude-mdgit clone --depth 1 https://github.com/cozystack/ccpWhat 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.00854 | $0.00854 |
| Opus 5 | $0.00427 | $0.00427 |
| Sonnet 5 | $0.00171 | $0.00171 |
| Haiku 4.5 | $0.00085 | $0.00085 |
Grade A, and why
ccp 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code when working with this repository.
What This Is
Cozystack Claude Plugins (CCP) — an external marketplace repository for Claude Code plugins for the Cozystack ecosystem.
Repository Structure
plugins/
<plugin-name>/
.claude-plugin/plugin.json # plugin metadata
skills/
<skill-name>/
SKILL.md # skill spec (frontmatter + workflow)
references/ # supporting docs the skill reads
.claude-plugin/
marketplace.json # registry; lists every plugin + description
tools/
check-refs.sh # cross-reference validator (CI gate)
.github/workflows/
validate.yml # PR validation: jq + check-refs.sh
README.md # operator-facing skill catalogue
CLAUDE.md # this file — contributor guidance
Two plugins ship today:
plugins/cozystack/— platform bundle (10 skills: wizard, talos-bootstrap, talos-reset, ubuntu-bootstrap, cluster-install, debug, cluster-upgrade, package-deploy, package-bump, external-app-create).plugins/linstor/— storage-recovery (1 skill: recover).
Multi-skill plugin shape: every plugin has one .claude-plugin/plugin.json at its root, and one directory per skill under skills/. Skills are addressed by Claude Code as /<plugin>:<skill> (e.g. /cozystack:wizard).
Adding a New Skill to an Existing Plugin
mkdir plugins/<plugin>/skills/<new-skill>/{references}(references optional).- Write
plugins/<plugin>/skills/<new-skill>/SKILL.mdwith YAML frontmatter (name:,description:, optionalargument-hint:). - Update
plugins/<plugin>/.claude-plugin/plugin.jsondescriptionto mention the new skill (the cross-reference checker intools/check-refs.shenforces this). - Update
.claude-plugin/marketplace.jsonplugins[].descriptionfor the parent plugin — list every skill the plugin ships. - Update
README.mdskills table. bash tools/check-refs.shlocally before commit.
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 First seen · 71 lines · 854 tokens per session scan A 1aff1b231ba5
ccp CLAUDE.md is an instructions file published in the GitHub repository cozystack/ccp (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 854 tokens to every session, about $0.0043 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.
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.