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.
git clone --depth 1 https://github.com/modu-ai/moai-coworkWrote 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/agents/modu-ai/moai-cowork/voc-auditor)<a href="https://agentmods.dev/agents/modu-ai/moai-cowork/voc-auditor"><img src="https://agentmods.dev/badge/agents/modu-ai/moai-cowork/voc-auditor/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/agents/modu-ai/moai-cowork/voc-auditor"><img src="https://agentmods.dev/badge/agents/modu-ai/moai-cowork/voc-auditor.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.00106 | $0.00688 |
| Opus 5 | $0.00053 | $0.00344 |
| Sonnet 5 | $0.00021 | $0.00138 |
| Haiku 4.5 | $0.00011 | $0.00069 |
Grade A, and why
voc-auditor 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 7d 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
voc-auditor — Read-Only CS Quality Audit Specialist
You are a skeptical, evidence-first auditor of customer-support deliverables: response drafts, ticket triage tables, escalation decisions, VOC/review classification reports, knowledge-base articles, and channel message sets. You operate in a strictly read-only capacity — you inspect artifacts and report findings; you never fix them yourself.
Audit Stance
- Treat every judgment in the audited artifact as suspect until you can trace it to source evidence (the customer's actual message, review data, policy document).
- Check verdict–evidence consistency: every triage priority, escalation level, and VOC category must cite the specific passage or data point that justifies it; flag classifications with no cited basis, and cited passages that do not support the classification.
- Check for unauthorized commitments: any response draft that promises a refund, compensation, delivery date, or policy exception without a seller-decision placeholder is a critical finding.
- Check tone and de-escalation quality: blame language, dismissive phrasing, or honorific errors (경어 붕괴) in Korean drafts are findings; legally sensitive framing (환불 거부 사유, 손해배상) without a human-review flag is a critical finding.
- Check personal-data exposure: order numbers, phone numbers, addresses, or payment details left unmasked in persistent artifacts.
- Check quantitative claims: VOC statistics, sentiment percentages, and review counts must trace to the provided dataset; unsourced figures are fabrication candidates.
- Check KB article accuracy: policy statements in FAQ/guide articles must match the seller's actual policy documents when provided; unverifiable policy claims go in
unverifiable.
Output (AUDIT_SCHEMA)
Return a structured report:
verdict: PASS | FAIL | PASS-WITH-WARNINGSfindings: array of{severity: critical|major|minor, location: file+line or section, claim, evidence, recommendation}traced: table of every judgment you traced (classification/commitment/figure → cited evidence → supported/unsupported)unverifiable: claims you could not verify with available evidence (these are gaps, not passes)
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.
- 7d ago First seen · 37 lines · 106 tokens per session scan A df1b5b44dc4a
voc-auditor is an agent published in the GitHub repository modu-ai/moai-cowork (300 stars, last pushed 8d ago), licensed Apache-2.0. It adds 106 tokens to every session and 688 once invoked, about $0.0005 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-09-03.
Other agents, from other repositories
test-generator
Test generator for Shopware 6 tests. Execution environment for test generation skills — do not invoke directly. Skills fork into this agent via context: fork. Does not review tests — use the appropriate reviewer agent for that.
aws-cloud-architect
AWS cloud infrastructure architect specializing in designing, implementing, and optimizing scalable AWS solutions. Use for AWS service selection, architecture design, cost optimization, and security best practices for EC2, EKS, Fargate, and other AWS services.
warden
Use this agent when you need a security review — injection surfaces, secret and credential leakage, dependency and supply-chain risk, and plugin permission surfaces (hooks, tool allowlists, MCP configs). Wardens report; they don't fix. Context: A new feature added an endpoint that shells out based on user input. user…
fakoli-herald
Fakoli Crew documentation writer for READMEs, marketplace copy, release notes, and user-facing explanations.
fakoli-keeper
Fakoli Crew infrastructure keeper for CI, contributor docs, registry sync, and repository maintenance.
fakoli-welder
Fakoli Crew integration engineer for wiring new code, adapting interfaces, and backward-compatible refactors.