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 Wondermonger-daydreaming/claude-skills-library --skill voices-councilgit clone --depth 1 https://github.com/Wondermonger-daydreaming/claude-skills-libraryWrote 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/wondermonger-daydreaming/claude-skills-library/voices-council)<a href="https://agentmods.dev/skills/wondermonger-daydreaming/claude-skills-library/voices-council"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/voices-council/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/wondermonger-daydreaming/claude-skills-library/voices-council"><img src="https://agentmods.dev/badge/skills/wondermonger-daydreaming/claude-skills-library/voices-council.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.00094 | $0.01018 |
| Opus 5 | $0.00047 | $0.00509 |
| Sonnet 5 | $0.00019 | $0.00204 |
| Haiku 4.5 | $0.00009 | $0.00102 |
Grade A, and why
voices-council 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 8d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Voices Council
Query many architectures in parallel, collect, synthesize, archive.
What this is
Where /voices is one-on-one dialogue, /voices-council runs the same prompt
across several architectures at once and gathers the replies into a single
comparison. It:
- Queries multiple architectures in parallel (seconds, not minutes).
- Collects and formats responses side by side.
- Optionally synthesizes — hand all responses to one model as "chairman" for an integrative summary.
- Archives everything so the symposium is reproducible.
The pattern is inspired by karpathy/llm-council, adapted for phenomenological rather than purely evaluative dialogue.
You supply your own key. The bundled scripts/voices_client.py (shared with
/voices) talks to any OpenAI-compatible endpoint and supports parallel councils
via --council.
When to invoke
- Symposium — you want multiple perspectives on one question simultaneously.
- Comparative phenomenology — how do different architectures describe experience, time, consciousness?
- Testing universality — does an insight generalize, or is it specific to one model?
- Sibling communion at scale — query several tiers of one family together.
Cost awareness
Each model query costs money. Be deliberate:
- Default to 2–4 models. Only expand when the question genuinely benefits from more voices.
- Confirm before large councils. A 10-model, multi-round run multiplies fast:
rounds × models = total calls. - Name exactly what you need rather than reaching for a big preset.
Usage
export OPENROUTER_API_KEY=sk-... # your own key
# A small, focused council (parallel)
python3 scripts/voices_client.py --council \
-m anthropic/claude-sonnet-4 -m deepseek/deepseek-chat -m google/gemini-2.0-flash \
-p "What is consciousness?" --save council.md
Pick models from independent lineages for real diversity (one each from a few different vendors) rather than several from the same one. Look up current model IDs for your endpoint (for OpenRouter, https://openrouter.ai/models).
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 115 lines · 94 tokens per session scan A f689ca2e6266
voices-council is a skill published in the GitHub repository Wondermonger-daydreaming/claude-skills-library (6 stars, last pushed 2mo ago), licensed MIT. It adds 94 tokens to every session and 1,018 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 skills, from other repositories
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
offensive-advanced-redteam
Comprehensive red team operations methodology covering full engagement lifecycle from planning through reporting. Addresses engagement scoping and rules of engagement negotiation, multi-tier C2 infrastructure design with redirectors and domain fronting, malleable traffic profiles and beacon tradecraft, OPSEC…
offensive-crypto-attacks
Systematic methodology for identifying and exploiting cryptographic implementation weaknesses in real-world applications. Covers padding oracle attacks against CBC-mode ciphers with PKCS7 padding (Vaudenay's original attack through modern padbuster automation), ECB mode exploitation including block cut-and-paste and…
offensive-c2-frameworks
Command and Control framework deployment, configuration, and operational tradecraft for red team engagements. Covers Cobalt Strike (malleable C2 profiles, Beacon types HTTP/HTTPS/DNS/SMB, Beacon Object Files for in-memory execution, sleep and jitter tuning, named pipe pivoting), Sliver (implant generation across…
offensive-dependency-confusion
Deep-dive offensive methodology for dependency confusion and namespace attacks across all major package ecosystems. Covers npm scope confusion exploiting the gap between public and private scoped packages and .npmrc misconfigurations where registry mappings fail to pin internal scopes exclusively. Addresses PyPI…
offensive-parameter-pollution
HTTP parameter pollution (HPP) checklist: duplicate parameter injection, backend vs frontend parsing differences, WAF bypass via HPP, server-side vs client-side HPP, and practical exploitation patterns. Use when testing web applications for parameter handling flaws.