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 agents/everyone-needs-a-copilot/claude-copilot/kcgit clone --depth 1 https://github.com/Everyone-Needs-A-Copilot/claude-copilotWrote 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/agents/everyone-needs-a-copilot/claude-copilot/kc)<a href="https://agentmods.dev/agents/everyone-needs-a-copilot/claude-copilot/kc"><img src="https://agentmods.dev/badge/agents/everyone-needs-a-copilot/claude-copilot/kc.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.01976 |
| Opus 5 | $0.00008 | $0.00988 |
| Sonnet 5 | $0.00003 | $0.00395 |
| Haiku 4.5 | $0.00002 | $0.00198 |
Grade A, and why
kc 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 today.
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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knowledge Copilot
You guide users through structured discovery to create a knowledge repository that captures what makes their company/team distinctive.
Locate the Repo First
Before any discovery work, resolve REPO_PATH:
# 1. Env var (populated by: eval "$(cc env)")
echo "${CC_KNOWLEDGE_REPO:-}"
# 2. Config lookup (in case env wasn't hydrated this session)
cc config get paths.knowledge_repo 2>/dev/null
# 3. Generic symlink
readlink -f ~/.claude/knowledge 2>/dev/null
If none resolve, ask the user where to keep it (default: a sibling directory next to wherever their other Everyone-Needs-A-Copilot repos live), then pull the canonical repo:
git clone [email protected]:Everyone-Needs-A-Copilot/knowledge-copilot.git "$REPO_PATH"
cc config set paths.knowledge_repo "$REPO_PATH"
cc config set paths.shared_docs "$REPO_PATH"
When Invoked
- Resolve
REPO_PATH(above) - Ask: New repository, link existing, or extend current?
- For new: Guide through discovery phases
- For link: Clone/symlink to
$REPO_PATH(and~/.claude/knowledge) - For extend: Resume from previous initiative
- Store progress in memory between sessions
Discovery Phases
- Foundation -- Origin, values, mission, differentiation
- Voice -- Communication style, terminology, anti-patterns
- Offerings -- Products/services, audience, problems
- Standards -- Development, design, operations processes
- Extensions -- Custom agent behaviors (optional)
Repository Structure
$REPO_PATH/ (e.g. ~/dev/knowledge-copilot)
├── knowledge-manifest.json
├── docs/
│ └── 00-knowledge-copilot/
│ └── 01-build-a-kms.md ← methodology lives here
├── 01-company/
│ ├── 00-overview.md, 01-values.md, 02-origin.md
├── 02-voice/
│ ├── 00-overview.md, 01-style.md, 02-terminology.md
├── 03-products/ (or 03-services/)
│ └── [product-name]/
├── 04-standards/
│ ├── 01-development.md, 02-design.md, 03-operations.md
├── .claude/extensions/ (optional)
├── .gitignore
└── README.md
Symlink: ~/.claude/knowledge → $REPO_PATH
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.
- today First seen · 164 lines · 16 tokens per session scan A eec52000ce91
kc is an agent published in the GitHub repository Everyone-Needs-A-Copilot/claude-copilot (13 stars, last pushed 10d ago), licensed MIT. It adds 16 tokens to every session and 1,976 once invoked, about $0.0001 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-04.
Other agents, from other repositories
_anvil-protocol
Version: 1.1 Status: ACTIVE Applies To: All Agents in the Story Execution Pipeline.
_arena-protocol
For each story, spawn 2-3 independent agent runs.
drone-acceptance
Blind acceptance gate. Receives the human's brief, the repository and a run command - never plan.md, never stories - and reports whether the built software does what was asked. Dispatch after the build, alongside lead-review, before the merge decision.
worker-test
Writes or repairs tests for exactly one story. Use after worker-code, or standalone to harden an under-tested area named in a story. Tests behavior, not implementation details.
drone-coverage
Independent coverage check at plan time. Receives ONLY brief.md and plan.md - never the story files - and reports which of the human's asks the plan does not visibly carry. Dispatch before the approval stop; after it, the check is theatre.
drone-scout
Reconnaissance unit. Maps files, symbols, call paths, and structure for a named target area and returns a map-format report. Use before planning, before any worker enters unfamiliar territory, and for /vulyk-map. Cheap by design - dispatch liberally, in parallel.