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 agentmods add skills/aigorahub/elves/setup-councilnpx skills add aigorahub/elves --skill setup-councilgit clone --depth 1 https://github.com/aigorahub/elvesWrote 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/aigorahub/elves/setup-council)<a href="https://agentmods.dev/skills/aigorahub/elves/setup-council"><img src="https://agentmods.dev/badge/skills/aigorahub/elves/setup-council.svg" alt="Measured on agentmods" 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.00025 | $0.00280 |
| Opus 5 | $0.00013 | $0.00140 |
| Sonnet 5 | $0.00005 | $0.00056 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
setup-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 6d 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.
What it actually says
Setup Council (Cobbler compatibility)
This is an Elves-managed Claude Code compatibility alias for /setup-council.
It delegates to the same Cobbler model onboarding / setup contract as /setup-cobbler,
references/model-onboarding.md, and
python3 scripts/cobbler_agents.py onboard plan|show|apply|probe and
python3 scripts/cobbler_agents.py setup. Council is a compatibility gathering name; Cobbler is the
coordinator.
Rules:
- Setup must not require OpenRouter or external keys.
- Do not print credentials or run paid model turns by default (live smoke is opt-in).
- Write only ignored local
.elves/models.tomlpreferences; Never stage secrets or that file. - Keep native-first defaults and host-native fallbacks.
- Interview → apply → probe; re-run to update choices later.
- Use the main
elvesskill for full setup wording and operator CLI flags.
Codex equivalent: $elves setup-council or natural language — not a top-level Codex slash command.
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.
- 6d ago First seen · 29 lines · 25 tokens per session scan A 2ae3d9e81f75
setup-council is a skill published in the GitHub repository aigorahub/elves (218 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 280 once invoked, about $0.0001 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-30.
Other skills, from other repositories
speckit-workflow
Comprehensive understanding of the spec-kit methodology. Constitution-driven feature development with specify, plan, tasks, and implement phases.
delegation-principle
Core principle that the main agent is a coordinator, not an implementer. All work must be delegated to subagents.
ralph-specum-start
This skill should be used only when the user explicitly asks to use $ralph-specum-start, or explicitly asks Ralph Specum in Codex to start or resume a spec.
ralph-specum-requirements
This skill should be used only when the user explicitly asks to use $ralph-specum-requirements, or explicitly asks Ralph Specum in Codex to run the requirements phase.
ralph-specum-cancel
This skill should be used only when the user explicitly asks to use $ralph-specum-cancel, or explicitly asks Ralph Specum in Codex to stop execution or remove a spec.
ralph-specum-prototype
This skill should be used only when the user explicitly invokes $ralph-specum-prototype, or explicitly asks Ralph Specum in Codex to run, resume, quick-run, or cancel an optional prototype.