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 aatirar/voc-claude-skills --skill voc-routegit clone --depth 1 https://github.com/aatirar/voc-claude-skillsWrote 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/aatirar/voc-claude-skills/voc-route)<a href="https://agentmods.dev/skills/aatirar/voc-claude-skills/voc-route"><img src="https://agentmods.dev/badge/skills/aatirar/voc-claude-skills/voc-route/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/aatirar/voc-claude-skills/voc-route"><img src="https://agentmods.dev/badge/skills/aatirar/voc-claude-skills/voc-route.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.00071 | $0.01405 |
| Opus 5 | $0.00036 | $0.00702 |
| Sonnet 5 | $0.00014 | $0.00281 |
| Haiku 4.5 | $0.00007 | $0.00140 |
Grade A, and why
voc-route 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 11d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/voc-route — Send Findings Where They Get Acted On
A synthesis report is intelligence. Nobody acts on intelligence; they act on a thing that landed on their desk with their name on it. This skill decides where each confirmed theme goes and carries the evidence along, so the receiving team never has to redo the analysis to trust it.
Requires
| What | Value |
|---|---|
| Input | outputs/voc/synthesis/<date>-confirmed.json |
| Config | context/product-context.md → routing_overrides, page_map |
| Cost | Free. No external calls unless you enable a push destination. |
The five destinations
1. Testimonial queue
Route when: praise is specific, attributable, and about a concrete outcome. The account is CRM-matched at tier A or B. The language would survive being put on a landing page.
Do not route generic praise. "Great product, easy to use" is worthless as a testimonial and using it signals you had nothing better.
Carries: verbatim quote, customer name and title, account context, suggested channels, and an explicit approval-required flag. Public use of a customer quote generally needs written permission regardless of where you found it — a G2 review is public, but re-publishing it in an ad with their logo is a different act. Never mark a quote approved from this skill.
2. Case-study leads
Route when: the customer described a before-and-after — a transformation, a measurable outcome, or a switching story. Active customer, tier A preferred.
Carries: the outcome arc in their own words, why this story is interesting, and a proposed
angle. The draft outreach email is generated by /voc-dispatch, not here.
3. Marketing objection map
Route when: a recurring prospect objection appears. This is the highest-leverage destination and the most commonly skipped.
Carries: the objection in prospect language, mention count, and the specific pages where it
should be addressed — resolved from page_map in your context file. An objection routed
without a page is a note; an objection routed to /pricing and /security is a task.
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.
- 11d ago First seen · 137 lines · 71 tokens per session scan A 9be947238abf
voc-route is a skill published in the GitHub repository aatirar/voc-claude-skills (0 stars, last pushed 25d ago), licensed MIT. It adds 71 tokens to every session and 1,405 once invoked, about $0.0004 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
bdr-enablement-generator
Generates account research briefs, personalized outreach sequences, persona-specific talk tracks, and objection handling frameworks for B2B SaaS BDR teams. Use when preparing BDR outreach for target accounts, building prospecting sequences, creating call scripts, developing objection responses, onboarding new BDRs, or…
competitive-battlecard-generator
Generates and maintains competitive battlecards from win/loss data, competitor intel, G2 reviews, and sales feedback. Use when building battlecards for a specific competitor, updating existing battlecards with new intel, preparing BDRs or AEs for competitive deals, analyzing win/loss patterns against a competitor, or…
marketing-ops-sop-generator
Generates standard operating procedures for B2B SaaS marketing operations: campaign naming conventions, UTM governance, tool administration, workflow QA, data hygiene, lead routing, and incident response playbooks. Use when setting up or auditing marketing ops processes, onboarding a new marketing ops hire…
abm-program-orchestrator
End-to-end ABM program design and orchestration for B2B SaaS mid-market and enterprise motions. Use when building a target account list, designing account tiering criteria, planning ABM channel orchestration, coordinating BDR outreach with marketing campaigns, defining ABM measurement frameworks, or running an ABM…
ceo-monthly-revenue-report-generator
Generates the monthly revenue-accountable marketing report that B2B SaaS marketing leaders deliver to CEOs, CFOs, executive teams, and boards. Use when preparing the monthly CEO report, drafting the marketing section of a board deck, defending budget decisions, diagnosing pipeline gaps, or transitioning marketing from…
account-research-brief-generator
Generates sourced, BDR-ready account research briefs for named target accounts in B2B SaaS ABM and outbound motions. Use after a target account list is built and before outreach sequences are written. Best for Tier 1, Tier 2, and intent-qualified accounts where BDRs need a clear "why this account, why now, why this…