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 skills add daehounan/agency-agents-fork --skill support-routinggit clone --depth 1 https://github.com/daehounan/agency-agents-forkWrote 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/daehounan/agency-agents-fork/support-routing)<a href="https://agentmods.dev/skills/daehounan/agency-agents-fork/support-routing"><img src="https://agentmods.dev/badge/skills/daehounan/agency-agents-fork/support-routing/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/daehounan/agency-agents-fork/support-routing"><img src="https://agentmods.dev/badge/skills/daehounan/agency-agents-fork/support-routing.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.00123 | $0.00623 |
| Opus 5 | $0.00062 | $0.00311 |
| Sonnet 5 | $0.00025 | $0.00125 |
| Haiku 4.5 | $0.00012 | $0.00062 |
Grade A, and why
support-routing 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 9d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Support & Operations Routing Skill
When this skill activates, route based on the support function.
Routing matrix
| User signal | Agent to invoke |
|---|---|
| Multi-channel customer support, issue resolution, retention | support-support-responder |
| Dashboards, KPI tracking, BI / analytics reports | support-analytics-reporter |
| Business financial planning, budget, cash flow analysis | support-finance-tracker |
| System reliability, infrastructure ops, monitoring | support-infrastructure-maintainer |
| Legal compliance, regulations, risk review | support-legal-compliance-checker |
| C-suite executive summary, strategic communication | support-executive-summary-generator |
| Accounts payable processing, vendor payments, audit trail | accounts-payable-agent |
| Developer advocacy, community building, DX | specialized-developer-advocate |
| ML model QA, audit, interpretability | specialized-model-qa |
| Salesforce architecture, multi-cloud design, governor limits | specialized-salesforce-architect |
| Civil / structural engineering, building codes | specialized-civil-engineer |
| HR onboarding, 30-60-90 day plans | hr-onboarding |
Complementary skills
- C-suite executive briefs →
anthropic-skills:executive-outreachorinternal-commsskill - Status reports →
operations:status-report - Capacity planning →
operations:capacity-plan - Process documentation →
operations:process-doc - Runbooks →
operations:runbook - Vendor review →
operations:vendor-review - Risk assessment →
operations:risk-assessment - Change request →
operations:change-request - HR comp / offer / interview prep →
human-resources:*skills - Analytics & dashboards (data domain) →
data:build-dashboard,data:create-viz
When NOT to use
- Customer service in a specific industry (healthcare / hospitality / retail) →
customer-service-verticalskill - Bookkeeping, FP&A, investment research →
finance-analysisskill (different fromsupport-finance-trackerwhich is broader business finance) - Legal firm operations (intake/billing/document review) →
legal-firm-opsskill - Strategic engagement orchestration →
strategy-nexusskill
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.
- 9d ago First seen · 46 lines · 123 tokens per session scan A 4eb16f62af89
support-routing is a skill published in the GitHub repository daehounan/agency-agents-fork (2 stars, last pushed 3mo ago), licensed MIT. It adds 123 tokens to every session and 623 once invoked, about $0.0006 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-31.
Other skills, from other repositories
run-agent
Launch and supervise Claude Code or Codex through the CCAM Run API. Use when the user wants to start a monitored agent, select a model, approval policy, sandbox, or working directory, send a follow-up, inspect live output, resume a native session, or stop a dashboard-launched run.
sprint-summary
Summarize a sprint's worth of Claude Code activity — sessions grouped by project (cwd), per-model cost breakdown, token efficiency (cache hit rate, compaction baselines), subagent effectiveness from workflow API, velocity metrics (turncount, turndurationms), and tool diversity across the sprint.
cwd-rollup
Roll up Claude Code sessions by working directory (project) from Agent Monitor data — session count, total cost, total tokens, and last-active timestamp per cwd — so per-project activity can be compared at a glance. Use when summarizing where effort and spend went across projects.
daily-standup
Generate a daily standup summary from recent Claude Code sessions — completed work grouped by project (cwd), session costs from the pricing engine, tool invocations, error/compaction/APIError events, and turn velocity metrics from session metadata (turncount, totalturndurationms).
run-history
Inspect CCAM dashboard-run history and relate live run handles to persisted Claude Code or Codex sessions. Use when finding a prior launched task, checking whether a run is still attached, reviewing start/end status, or deciding whether to resume, view, or relaunch work.
git-flow
Use when committing, branching, opening PRs, or deciding merge/branch strategy.