What is kc-claude-plugins CLAUDE.md?

Repository instructions for maintaining a collection of seven coding-agent plugins. A monorepo is one repository that contains several related projects, and release-please is a tool that prepares version changes and release notes automatically.

Use it when developing or reviewing plugin changes, following the required commit and release process, and checking the repository's pre-merge and release tests.

It gives contributors shared rules for changing plugins, preparing pull requests, and releasing versions without editing release data by hand.

How iamcxa/kc-claude-plugins configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to iamcxa/kc-claude-plugins. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/iamcxa/kc-claude-plugins/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/iamcxa/kc-claude-plugins

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/iamcxa/kc-claude-plugins/claude-md/github.svg)](https://agentmods.dev/instructions/iamcxa/kc-claude-plugins/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/iamcxa/kc-claude-plugins/claude-md"><img src="https://agentmods.dev/badge/instructions/iamcxa/kc-claude-plugins/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/iamcxa/kc-claude-plugins/claude-md"><img src="https://agentmods.dev/badge/instructions/iamcxa/kc-claude-plugins/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 2,427 This file is loaded in full into every session.

When invoked 2,427 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.02427	$0.02427
Opus 5.5	$0.00971	$0.00971
Sonnet 5.5	$0.00485	$0.00485
Haiku 4.5	$0.00243	$0.00243

Measured 14d ago against content hash e593b9e317af, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

kc-claude-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 14d 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.

CLAUDE.md · 116 lines

How it starts

The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.

kc-claude-plugins

Public marketplace repo containing eleven plugins: e2e-pipeline, kc-plugin-forge, kc-nightwatch, kc-hyperfocus, kc-team-ops, kc-pr-flow, kc-dev-flow, kc-dev-flow-2, kc-journey-map, kc-ship-flow, and kc-adr. Plugins may keep their own CLAUDE.md for plugin-internal conventions. This file documents repo-wide rules that apply to PRs touching any plugin or the marketplace manifest.

Plugin Versioning & Release — release-please (MANDATORY)

Versioning, tagging, and changelogs are owned by release-please (monorepo manifest mode, one independent component per plugin — see release-please-config.json + .release-please-manifest.json). Do not hand-bump versions in a feature PR. A feature PR touches only its plugin's files (<plugin>/**) using Conventional Commits; the version bump is proposed automatically.

How a release happens

Feature PR — implement under <plugin>/, Conventional-Commit scoped to that plugin (feat(<plugin>): … / fix(<plugin>): …). No version edits, no marketplace / codex manifest edits for versioning. Squash-merge to main.
Release PR (automatic) — on push to main, .github/workflows/release-please.yml opens/updates a Release PR that, per changed plugin, bumps the version across <plugin>/.claude-plugin/plugin.json, <plugin>/.codex-plugin/plugin.json, and that plugin's .claude-plugin/marketplace.json entry (version string only — the bespoke marketplace description/keywords are never touched), and writes <plugin>/CHANGELOG.md.
Merge the Release PR — release-please cuts the <plugin>-vX.Y.Z tag + GitHub Release. A RELEASE_PLEASE_TOKEN PAT is required so the bot-opened Release PR fires the required status checks — see the comment in release-please.yml.

New components inherit the repository's explicit initial-version: 0.1.0 policy. Cross-repository adopters must pin only an actually published tag after the Release PR merges; never prepare a final dependency pin from a predicted release version.

Read the full file on GitHub · 116 lines

Changes

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.

14d ago Changed · +1 lines · +5 tokens per session e593b9e317af
15d ago Changed · +10 tokens per session 3971eb4d520f
24d ago Changed · +7 tokens per session ac50fada04c3
1mo ago Changed · -3 lines · -84 tokens per session 01209600faf1
1mo ago Changed · +27 tokens per session a969c328ddd8
2mo ago Changed · +14 lines · +249 tokens per session c6ac84eb1509
2mo ago First seen · 104 lines · 2,213 tokens per session scan A e9583375d463

Subscribe to this mod's changes

kc-claude-plugins CLAUDE.md is an instructions file published in the GitHub repository iamcxa/kc-claude-plugins (3 stars, last pushed today), licensed MIT. It adds 2,427 tokens to every session, about $0.0097 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.

Git and workflow Releases

kc-claude-plugins CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
kc-claude-plugins CLAUDE.mdiamcxa/kc-claude-plugins	Instructions file	3	today	MIT	A	2,427	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

kc-claude-plugins: Instructions file for Claude Code