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 golemfoundation/octant-council-builder --skill setupgit clone --depth 1 https://github.com/golemfoundation/octant-council-builderWrote 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/golemfoundation/octant-council-builder/setup)<a href="https://agentmods.dev/skills/golemfoundation/octant-council-builder/setup"><img src="https://agentmods.dev/badge/skills/golemfoundation/octant-council-builder/setup/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/golemfoundation/octant-council-builder/setup"><img src="https://agentmods.dev/badge/skills/golemfoundation/octant-council-builder/setup.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.00013 | $0.04262 |
| Opus 5 | $0.00006 | $0.02131 |
| Sonnet 5 | $0.00003 | $0.00852 |
| Haiku 4.5 | $0.00001 | $0.00426 |
Grade A, and why
setup 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 9d 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 — 527 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Council Design — Design Your Evaluation Council
A planning skill that guides the user through designing a custom evaluation council. Two phases: conversational discovery → structured design → plan, then implementation via research/generate/document agents.
Plan mode handles the plan file natively — no manual file writing needed.
Step 1: Enter Plan Mode
EnterPlanMode
Step 2: Dream Extraction
If $ARGUMENTS is empty, ask first:
AskUserQuestion:
question: "What domain should this council evaluate?"
header: "Council Domain"
options:
- label: "Public goods projects"
description: "General-purpose evaluation for funding decisions"
- label: "DeFi protocols"
description: "Evaluate DeFi projects on security, TVL, governance"
- label: "L2 rollups"
description: "Evaluate Layer 2 scaling solutions"
- label: "Research grants"
description: "Evaluate academic/applied research proposals"
- label: "Other"
description: "Describe your domain"
Store the answer as $DOMAIN. If "Other", use a follow-up text question.
Invoke the conversation sub-skill:
<skill name="council:design-conversation" args="$DOMAIN" />
(If $ARGUMENTS was provided, use it directly as the args.)
This runs a pure conversational dialogue — no structured questions, no tools. It returns a summary with:
- Domain — what we're evaluating
- Purpose — what decision this informs
- Data priorities — top data sources
- Evaluation priorities — the lenses that matter
- Skeptic focus — domain-specific red flags
- Out of scope — what the council won't assess
- Core essence — the ONE non-negotiable
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.
- 9d ago First seen · 527 lines · 13 tokens per session scan A 7d18f4edf598
setup is a skill published in the GitHub repository golemfoundation/octant-council-builder (3 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 4,262 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-31.
Other skills, from other repositories
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
anti-patterns
Catalogue of known SDLC anti-patterns that greatcto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
cost-model
Standardized cost-estimation framework for greatcto plans. Forces explicit LLM cost, infra cost, human-supervision time, and the (defensible) human-equivalent comparison. Output format is parsable by the board's /api/cost path — must follow exactly.
migration-ready-schema
Data-model rules that make a schema importable from day one, so the migration-import-engineer is never blocked on missing columns. Every SMB Product-Builder product must let a customer bring their data from an incumbent (ServiceTitan/Toast/Mindbody/Shopify) — that requires provenance (sourceref) and rollback…
stack-baseline
The pinned default technology stack for SMB Product-Builder products. One source of truth so the architect, app-scaffolder, auth-engineer, and senior-dev never re-decide the stack per build — they build ON it. Covers framework, ORM/DB, auth, UI, payments/email/SMS, files, jobs, testing, hosting, and observability…
agent-workflow-playbook
AI Agent Workflow & Skill Architecture Guide — turn expert work into measurable, reusable agent systems. Covers workflow discovery, skill decomposition, harness design, evaluation, human escalation, observability, cost control, and multi-agent orchestration. Includes a measured marketing-delivery case: 15 people × 3–4…