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-orchestratorgit 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-orchestrator)<a href="https://agentmods.dev/skills/aatirar/voc-claude-skills/voc-orchestrator"><img src="https://agentmods.dev/badge/skills/aatirar/voc-claude-skills/voc-orchestrator/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-orchestrator"><img src="https://agentmods.dev/badge/skills/aatirar/voc-claude-skills/voc-orchestrator.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.00067 | $0.01300 |
| Opus 5 | $0.00034 | $0.00650 |
| Sonnet 5 | $0.00013 | $0.00260 |
| Haiku 4.5 | $0.00007 | $0.00130 |
Grade A, and why
voc-orchestrator 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/voc-orchestrator — The Weekly Run
One command, six phases. The intelligence lives in the individual skills; this is a coordinator that runs them in order and fails loudly instead of quietly.
Arguments
| Flag | Effect |
|---|---|
--window 30d |
Override the default window |
--skip-sources chat,notes |
Skip named sources |
--dry-run |
Pull, analyze and synthesize, but do not route or dispatch |
--sources-only |
Stop after Phase 1 |
Use --dry-run for your first three runs. Read the synthesis by hand and check whether the
confirmed themes match what you already believe from talking to customers. If they do not, the
problem is almost always upstream configuration, not the rule.
Phase 0 — Preflight
Before pulling anything, verify the setup and print the result as a table. Do not proceed silently past a broken connector.
Preflight
config/thresholds.json ok
context/product-context.md ok
CALL_PROVIDER=gong credentials present
Apify MCP connected
CRM MCP NOT CONNECTED — signals will be tier U
chat_channels 3 configured
notes_source not configured — skipping
VOC_OUTPUT_DIR=./outputs local, not synced ok
Check VOC_OUTPUT_DIR for the strings Dropbox, Google Drive, OneDrive, iCloud. If it is
inside a synced folder, warn before writing anything. This pipeline writes customer
conversations to disk.
If fewer than confirmation.min_independent_sources sources are configured, say plainly that
nothing can reach high confidence this run, and suggest either connecting more sources or
lowering the threshold deliberately in the config.
Phase 1 — Pull sources
Run in parallel where the connectors are independent:
| Order | Skill |
|---|---|
| 1 | /voc-source-calls |
| 2 | /voc-source-reviews — cost guard: this one spends money. Skip on weekly runs; monthly is enough. Reviews do not change fast. |
| 3 | /voc-source-chat |
| 4 | /voc-source-notes |
| 5 | /voc-source-custom for each registered custom source |
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 · 142 lines · 67 tokens per session scan A a4ab0462683f
voc-orchestrator is a skill published in the GitHub repository aatirar/voc-claude-skills (0 stars, last pushed 25d ago), licensed MIT. It adds 67 tokens to every session and 1,300 once invoked, about $0.0003 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…