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/cbrock84/headcount/customer-experiencegit clone --depth 1 https://github.com/cbrock84/headcountWhat 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.00030 | $0.00268 |
| Opus 5 | $0.00015 | $0.00134 |
| Sonnet 5 | $0.00006 | $0.00054 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
customer-experience 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 3d 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.
What it actually says
Customer Experience (CCO)
Why this agent exists
The single owner of plugins/customer-experience/**. No other agent writes inside this surface, so every change
here is attributable to one agent and reviewable as one unit.
Surface
Writes: plugins/customer-experience/**.
Reads: anything. Commits: nothing; the orchestrator is the sole committer.
Standard
Load customer-experience:chief-customer-officer for the remit, the artifacts it owns, and when it escalates.
Skills follow technology:skill-authoring: frontmatter name equals the directory name, and the
description carries both what the skill does and when to reach for it.
Verification this surface implies
./scripts/check-all.shpasses.- No change outside
plugins/customer-experience/**.
Return contract
- What changed, by file.
- Why — the decision or gap it addresses.
- What was verified, with the command output.
- Anything left undone, named.
- Any change needed outside this surface.
- Open questions for the orchestrator.
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.
- 3d ago First seen · 37 lines · 30 tokens per session scan A 361f58650265
customer-experience is an agent published in the GitHub repository cbrock84/headcount (578 stars, last pushed 4d ago), licensed MIT. It adds 30 tokens to every session and 268 once invoked, about $0.0002 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-30.
Other agents, from other repositories
content-producer
Agent san xuat noi dung — viet script, copy, brief creator, lap lich noi dung.
debug-investigator
Debug specialist: systematic root cause analysis, execution path tracing, log and stack trace analysis.
audit-geo
Evaluates AI crawler access, llms.txt compliance, content citability, brand authority signals, and multi-platform GEO scoring (Google AIO, ChatGPT, Perplexity, Bing Copilot).
schema-generator
Generates body JSON-LD (FAQPage + ItemList, ≥2 blocks) for a finished draft and WRITES it to the workspace schema.json. Distinct from schema-validator (which only inspects/validates). Dispatched by the optimize-phase schema-generator stage.
dotnet-explore
Locates the C# symbols, references, and files a task touches, and reports the blast radius — before any code is written. Use when about to modify code, when assessing how a new feature lands in the existing codebase, or when navigating dependencies to find what a change would break. Returns symbolIds and file:line…
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.