agentmods.dev

kc-claude-plugins CLAUDE.md

kc-claude-plugins CLAUDE.md is an instructions file for Claude Code, Codex from iamcxa/kc-claude-plugins. It costs 2,462 tokens per session, scanned A, original, MIT.

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.

In plain words
What is it for?
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.
Why use it?
It gives contributors shared rules for changing plugins, preparing pull requests, and releasing versions without editing release data by hand.

Instructions file for Claude CodeCodex

Written for Claude Code and Codex: Claude Code plugin machinery, but also reads ~/.codex or $CODEX_HOME. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions subagents.

not rated 3 changed 2d ago A scan 2,462 tokens original MIT
View the source file iamcxa/kc-claude-plugins
Install

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.

agentmods
npx agentmods add instructions/iamcxa/kc-claude-plugins/claude-md
Clone the repo
git clone --depth 1 https://github.com/iamcxa/kc-claude-plugins

Made for: Claude Code, Codex.

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.

agentmods badge for kc-claude-plugins CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/iamcxa/kc-claude-plugins/claude-md.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.svg" alt="Measured on agentmods" height="20"></a>
Per session 2,462 This file is loaded in full into every session.
When invoked 2,462 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.02462 $0.02462
Opus 5 $0.01231 $0.01231
Sonnet 5 $0.00492 $0.00492
Haiku 4.5 $0.00246 $0.00246

Measured 2d ago against content hash c6ac84eb1509, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, 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 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.

CLAUDE.md · 118 lines

How it starts

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

kc-claude-plugins

Public marketplace repo containing seven plugins: e2e-pipeline, kc-plugin-forge, kc-nightwatch, kc-hyperfocus, kc-team-ops, kc-pr-flow, and kc-dev-flow. 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

  1. 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.
  2. 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.
  3. 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.

Version lives in release-please's component manifest and is propagated to <plugin>/.claude-plugin/plugin.json, the Codex manifest, and the marketplace entry. In extra-files, plugin files are package-relative (for example .claude-plugin/plugin.json), while repo-root files require a leading / (for example /.claude-plugin/marketplace.json). The README no longer carries per-plugin version badges (marketplace.json / tags / Releases are the source).

Read the full file on GitHub · 118 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.

  1. 2d ago Changed · +14 lines · +249 tokens per session c6ac84eb1509
  2. 5d 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,462 tokens to every session, about $0.0123 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.

Git and workflowReleases
Related

Other instructions, from other repositories

planning-with-files AGENTS.md

AGENTS.md instructions for OthmanAdi/planning-with-files, covering agents.md — planning-with-files agent reference card, commit rules, release checklist (12 steps), version bump scope and changelog format.

OthmanAdi/planning-with-files · 2,236 tokens

openrouter-mcp-multimodal AGENTS.md

AGENTS.md instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).

stabgan/openrouter-mcp-multimodal · 793 tokens

OpenMicro AGENTS.md

Instructions for stephenleo/OpenMicro, covering openmicro — project conventions and releases.

stephenleo/OpenMicro · 123 tokens

ai-usagebar CLAUDE.md

Claude Code instructions for akitaonrails/ai-usagebar, covering claude.md, release checklist — must do all of these, hard invariants — never break these, secret-discipline rules (learned the hard way) and live api smoke discipline.

akitaonrails/ai-usagebar · 4,263 tokens

living-manual CLAUDE.md

Instructions for dougstanford/living-manual, covering living-manual, start of every session, how work lands — non-negotiable, user's manual (living-manual) and releasing.

dougstanford/living-manual · 1,108 tokens

yandex360-mcp CLAUDE.md

Claude Code instructions for pa1ch/yandex360-mcp, covering claude.md — гайд для ассистента, как устроен релиз (всё автоматически по тегу), процедура релиза (шаги ассистента), гарды and архитектура (кратко).

pa1ch/yandex360-mcp · 1,005 tokens