What is voc-source-custom?

An adapter for adding customer feedback from sources not covered by dedicated connectors, such as surveys, support tickets, email threads, community posts, churn interviews, app reviews, and sales-loss records. It converts each item into a standard format for the customer-feedback pipeline.

It helps bring additional feedback into the pipeline through an MCP server, an API, or an export file. It is used when adding sources such as NPS comments, support cases, forum posts, or app-store reviews.

It removes the need to build a separate processing method for every feedback source. Required details such as the exact wording, company, date, and source are recorded so later steps can interpret the signal honestly.

voc-source-custom — Skill for Claude Code by aatirar/voc-claude-skills

Install

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.

Any agent

npx skills add aatirar/voc-claude-skills --skill voc-source-custom

Clone the repo

git clone --depth 1 https://github.com/aatirar/voc-claude-skills

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/aatirar/voc-claude-skills/voc-source-custom/github.svg)](https://agentmods.dev/skills/aatirar/voc-claude-skills/voc-source-custom)

Your own site

<a href="https://agentmods.dev/skills/aatirar/voc-claude-skills/voc-source-custom"><img src="https://agentmods.dev/badge/skills/aatirar/voc-claude-skills/voc-source-custom/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/aatirar/voc-claude-skills/voc-source-custom"><img src="https://agentmods.dev/badge/skills/aatirar/voc-claude-skills/voc-source-custom.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 83 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,390 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00083	$0.01390
Opus 5.5	$0.00033	$0.00556
Sonnet 5.5	$0.00017	$0.00278
Haiku 4.5	$0.00008	$0.00139

Measured 2mo ago against content hash ea40105c843b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

voc-source-custom 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 2mo 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.

.claude/skills/voc-source-custom/SKILL.md · 138 lines

How it starts

The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/voc-source-custom — Bring Your Own Source

The pipeline does not care where a signal came from. It cares that the signal arrives in a known shape with honest metadata. This skill is the on-ramp for everything the dedicated source skills do not cover.

Common uses: NPS and survey open-text, support tickets, CRM email threads, community and forum posts, churn exit interviews, app store reviews, sales-lost reason fields, win/loss interviews.

Requires

What	Value
Access	An MCP server, an API you can call from Bash, or an export file
Config	`context/product-context.md` → `custom_sources`
Cost	Depends on the source. Most are free.

The contract

Every signal file written anywhere under outputs/voc/sources/ must have this shape. Get this right and everything downstream works without modification.

{
  "channel": "survey",
  "verbatim": "exact text as the customer wrote or said it",
  "fidelity": "verbatim",
  "company": "Northwind Trading",
  "speaker_role": "Operations Director",
  "date": "2026-04-22",
  "signal_type": "pain",
  "source_link": "https://...",
  "source_file": "outputs/voc/sources/survey/raw-2026-04-22.json",
  "notes": "NPS detractor, score 4"
}

Field	Rule
`channel`	A new, distinct name. This is what the confirmation rule counts. Do not reuse an existing channel name for a different source — and do not invent two names for the same source, which manufactures false corroboration.
`verbatim`	Exact. No cleanup.
`fidelity`	`verbatim` or `summarized`. Be honest; `/voc-dispatch` gates testimonial use on it.
`company`	`null` if unknown. Becomes tier U. That is fine.
`date`	When the customer said it, not when you exported it.
`signal_type`	`pain` \| `request` \| `praise` \| `objection` \| `competitive` \| `churn_reason`

Execution

Step 1 — Register the source

Add it to custom_sources in your context file:

custom_sources:
  - name: nps
    channel: survey
    method: api          # api | mcp | file
    endpoint: "https://api.example.com/responses"
    auth_env: SURVEY_API_KEY
    text_field: comment
    date_field: submitted_at
    filter: "score <= 6"

Read the full file on GitHub · 138 lines

Changes

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.

2mo ago First seen · 138 lines · 83 tokens per session scan A ea40105c843b

Subscribe to this mod's changes

voc-source-custom is a skill published in the GitHub repository aatirar/voc-claude-skills (0 stars, last pushed 2mo ago), licensed MIT. It adds 83 tokens to every session and 1,390 once invoked, about $0.0003 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-08-31.

Claude Code Research ai-agents b2b-saas claude-skills customer-research gong

voc-source-custom next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
voc-source-customaatirar/voc-claude-skills	Skill	0	2mo ago	MIT	A	83	Claude Code
bdr-enablement-generatorStallin-Sanamandra/b2b-saas-marketing-skills	Skill	7	6mo ago	MIT	A	131	Claude Code, Codex
competitive-battlecard-generatorStallin-Sanamandra/b2b-saas-marketing-skills	Skill	7	6mo ago	MIT	A	153	Claude Code, Codex
marketing-ops-sop-generatorStallin-Sanamandra/b2b-saas-marketing-skills	Skill	7	6mo ago	MIT	A	160	Claude Code, Codex
abm-program-orchestratorStallin-Sanamandra/b2b-saas-marketing-skills	Skill	7	6mo ago	MIT	A	148	Claude Code, Codex
ceo-monthly-revenue-report-generatorStallin-Sanamandra/b2b-saas-marketing-skills	Skill	7	6mo ago	MIT	A	121	Claude Code, Codex
account-research-brief-generatorStallin-Sanamandra/b2b-saas-marketing-skills	Skill	7	6mo ago	MIT	A	122	Claude Code, Codex