kc-team-ops

kc-team-ops is a plugin for Claude Code from iamcxa/kc-claude-plugins. Its manifest loads nothing; the 8 skills, 3 agents it bundles cost 648 tokens per session together, scanned A, original, MIT.

A team-operations toolkit for engineering managers, covering issue triage, project updates, codebase exploration, planning reviews, and team context. It connects product and engineering information to support structured decisions.

In plain words
What is it for?
Use it to triage work, decompose issues, track project health, review plans, maintain team context, and create user-journey maps.
Why use it?
It brings scattered project, team, customer, and codebase information into one workflow when deciding what needs investigation and how deeply to plan it.

Plugin for Claude Code

Written for Claude Code: a Claude Code plugin manifest. Also seen: mentions subagents.

Good fit Use it to triage work, decompose issues, track project health, review plans, maintain team context, and create user-journey maps.

Compare 6 plugins from other repositories ↓
Install in Claude Code
/plugin marketplace add iamcxa/kc-claude-plugins/plugin install kc-team-ops
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.

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.

agentmods badge for kc-team-ops

README.md
[![agentmods](https://agentmods.dev/badge/plugins/iamcxa/kc-claude-plugins/kc-team-ops/github.svg)](https://agentmods.dev/plugins/iamcxa/kc-claude-plugins/kc-team-ops)
Your own site
<a href="https://agentmods.dev/plugins/iamcxa/kc-claude-plugins/kc-team-ops"><img src="https://agentmods.dev/badge/plugins/iamcxa/kc-claude-plugins/kc-team-ops/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.

agentmods 80×15 button for kc-team-ops

Your own site · 80×15
<a href="https://agentmods.dev/plugins/iamcxa/kc-claude-plugins/kc-team-ops"><img src="https://agentmods.dev/badge/plugins/iamcxa/kc-claude-plugins/kc-team-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured The manifest loads nothing itself; its 8 skills, 3 agents cost 648 tokens a session between them.
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.
Security

Grade A, and why

kc-team-ops 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 6d 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.

kc-team-ops/.claude-plugin/plugin.json · 31 lines

What it actually says

{
  "name": "kc-team-ops",
  "description": "Team operations pipeline — EM triage with strategic lens (depth-adaptive routing, team context cache), project pulse updates, codebase exploration, issue decomposition, structured Linear management, EM plan/project review (keystone verification + cross-model pressure-test), evidence-cited user journey maps checked against the code (FigJam or HTML/PNG), and on-demand cross-model second opinion via Google's agy / Antigravity CLI (/gemini review|challenge|consult)",
  "version": "1.7.0",
  "author": {
    "name": "Kent Chen",
    "url": "https://github.com/iamcxa"
  },
  "license": "MIT",
  "keywords": [
    "team-ops",
    "em",
    "triage",
    "linear",
    "project-pulse",
    "issue-decomposition",
    "research",
    "subagents",
    "strategic-lens",
    "context-cache",
    "plan-review",
    "keystone-verification",
    "gemini",
    "cross-model",
    "second-opinion",
    "journey-map",
    "user-journey",
    "figjam"
  ]
}
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. 6d ago First seen · 31 lines scan A 903a99a2b648

Subscribe to this mod's changes

kc-team-ops is a plugin published in the GitHub repository iamcxa/kc-claude-plugins (3 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-03.