Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add iamcxa/kc-claude-plugins/plugin install kc-team-opsWrote 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.
[](https://agentmods.dev/skills/iamcxa/kc-claude-plugins/kc-em-sync)<a href="https://agentmods.dev/skills/iamcxa/kc-claude-plugins/kc-em-sync"><img src="https://agentmods.dev/badge/skills/iamcxa/kc-claude-plugins/kc-em-sync/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.
<a href="https://agentmods.dev/skills/iamcxa/kc-claude-plugins/kc-em-sync"><img src="https://agentmods.dev/badge/skills/iamcxa/kc-claude-plugins/kc-em-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00059 | $0.01183 |
| Opus 5 | $0.00030 | $0.00592 |
| Sonnet 5 | $0.00012 | $0.00237 |
| Haiku 4.5 | $0.00006 | $0.00118 |
Grade A, and why
kc-em-sync 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 7d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EM Team Context Sync
Fetch team strategic context from Linear and cache as YAML for use by EM triage.
Arguments
| Invocation | Behavior |
|---|---|
/kc-em-sync |
Interactive: list teams via list_teams, user picks one |
/kc-em-sync <team-name> |
Direct sync for named team |
/kc-em-sync --all |
Sync all previously synced teams (read existing YAML files in ~/.claude/kc-team-ops/) |
Process
1. Resolve Team
- If team name provided →
list_teams→ find matching team → getteam_id - If no argument →
list_teams→ present list → user picks - If
--all→ read~/.claude/kc-team-ops/*.yaml→ extract team names → sync each
2. Parallel Fetch
Fetch all data sources concurrently:
| Source | Linear MCP Call | Filter |
|---|---|---|
| Initiatives | list_initiatives |
status: active only |
| Projects | list_projects per initiative |
All statuses (show planned too) |
| Members | list_users(teamId) |
Active members |
| Cycles | list_cycles(teamId) |
Current + next (type current, next) |
| Recent issues | list_issues(teamId, limit: 10) |
For estimate scale inference |
| Customers | list_customers(includeNeeds: true) |
All customers with needs |
3. Infer Estimate Scale
Follow ${CLAUDE_PLUGIN_ROOT}/reference/estimate-inference.md logic:
- Read recent issues'
estimate.namevalues - Determine scale (T-shirt / Fibonacci / Linear / Exponential / Unknown)
- If Unknown → note in YAML, will prompt user during triage
4. Assemble & Write YAML
Write to ~/.claude/kc-team-ops/<team-name>-context.yaml:
team: <team-name>
team_id: "<id>"
synced_at: "<ISO 8601 timestamp>"
freshness_hours: 3
initiatives:
- id: "<id>"
name: "<name>"
status: active
projects:
- id: "<id>"
name: "<name>"
status: "<status>"
lead: "<assignee name>"
target: "<target date or null>"
customers:
- id: "<id>"
name: "<name>"
needs:
- id: "<id>"
title: "<title>"
priority: "<urgency value>"
linked_issues: ["<issue identifier>", ...]
linked_project: "<project id or null>"
members:
- id: "<id>"
name: "<display name>"
role: "<role or 'member'>"
active_cycle:
id: "<id>"
name: "<name>"
starts: "<date>"
ends: "<date>"
next_cycle:
id: "<id>"
name: "<name>"
starts: "<date>"
ends: "<date>"
estimate_scale: "<tshirt|fibonacci|linear|exponential|unknown>"
estimate_values: ["<value1>", "<value2>", ...]
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.
- 7d ago First seen · 129 lines · 59 tokens per session scan A e217aa1ecc0b
kc-em-sync is a skill published in the GitHub repository iamcxa/kc-claude-plugins (3 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 1,183 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.