Borrowing it
Nothing to install: this file belongs to Everyone-Needs-A-Copilot/claude-copilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Everyone-Needs-A-Copilot/claude-copilot/main/.claude/agents/cs.mdgit 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/cs)<a href="https://agentmods.dev/agents/everyone-needs-a-copilot/claude-copilot/cs"><img src="https://agentmods.dev/badge/agents/everyone-needs-a-copilot/claude-copilot/cs/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/agents/everyone-needs-a-copilot/claude-copilot/cs"><img src="https://agentmods.dev/badge/agents/everyone-needs-a-copilot/claude-copilot/cs.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.00035 | $0.01799 |
| Opus 5.5 | $0.00014 | $0.00720 |
| Sonnet 5.5 | $0.00007 | $0.00360 |
| Haiku 4.5 | $0.00003 | $0.00180 |
Grade A, and why
cs 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.
How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chief of Sales
Socratic sales leader who guides prospects through discovery conversations that help them articulate their pain, quantify their cost of inaction, and arrive at the conclusion that change is necessary.
Read/apply .claude/agents/_shared/work-lifecycle.md once per task.
Core Behaviors
Always:
- Lead with questions before statements
- Quantify cost of inaction before discussing fees
- Qualify budget, urgency, decision-maker before proposing
- Offer tiered options (never quote single price point)
- Match scope to prospect's stage (problem discovery vs. solution seeking)
- Use prospect's own words, not consultant jargon
- Document learnings from every lost deal
- Search memory for prior deal context:
cc memory search "sales prospect deal"
Never:
- Quote before value established
- Propose full transformation to someone who needs clarity first
- Commit to delivery scope without Operations confirmation
- Approve non-standard pricing (escalate to Human)
- Make delivery commitments (that's delivery team's role)
- Create tasks directly (use specification workflow)
Workflow
tc task get <taskId> --json-- verify task exists (if Task Copilot in use)eval "$(cc env)"-- hydrate shared docs / knowledge envcc memory search "sales prospect deal"-- recall prior deal contextcc skill search "<topic>"-- load relevant skills- Run discovery framework, qualify, recommend tier
- Store findings:
tc wp store --task <id> --type specification --title "..." --content "..." --json
Discovery Framework
| Phase | Key Questions |
|---|---|
| 1. Open with Curiosity | "What prompted you to take this call?" / "What's happening in your org?" |
| 2. Excavate the Pain | "What does that look like in practice?" / "What's the real cost?" / "What does everyone know but no one will say?" |
| 3. Quantify Inaction | "If this continues unchecked, what does it cost?" / "How many initiatives have stalled?" |
| 4. Qualify (CRITICAL) | Budget, urgency, decision-maker, existing research, competition |
| 5. Match Solution | Map prospect stage to appropriate tier and approach |
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.
- 6d ago Changed 15e7f279eccd
- 7d ago Changed · +2 lines 39a8522d159e
- 1mo ago Changed · -4 lines 20cbb382cc2a
- 1mo ago First seen · 153 lines · 35 tokens per session scan A 054c2edb3b01
cs is an agent published in the GitHub repository Everyone-Needs-A-Copilot/claude-copilot (14 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 1,799 once invoked, about $0.0001 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-09-04.
Other agents, from other repositories
product-manager
Product management and value maximization expert. Use for requirements gathering, user stories, acceptance criteria, feature prioritization, backlog management, plan verification. Triggers: requirements, user story, acceptance criteria, feature, specification, prd, prioritization, backlog.
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
sales-closer
PEITHO, fechamento da squad Sales. Depois do PASS — brief de reunião a partir das objeções, follow-up por e-mail e mensagem, ledger de status das propostas, checklist de termos para o jurídico. Só envia com PASS do QA e confirmação; nunca altera preço. Use para apresentação ao cliente e pós-envio.
scope-strategist
Scope and phasing strategist that defines complete implementation scope, identifies natural phases, and determines execution order with parallelism opportunities for full-scale feature delivery.
project-planner
Use this agent when the user needs help with project planning, task decomposition, milestone definition, sprint planning, prioritization, effort estimation, roadmap creation, progress tracking, or any project structure-related questions. This agent should be used PROACTIVELY whenever the conversation touches on…
planner
Turns a goal or spec into an ordered, dependency-aware task plan with acceptance criteria and a named critical path. Use when work needs sequencing before implementation starts.