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 evaluategit 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/evaluate)<a href="https://agentmods.dev/skills/golemfoundation/octant-council-builder/evaluate"><img src="https://agentmods.dev/badge/skills/golemfoundation/octant-council-builder/evaluate/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/evaluate"><img src="https://agentmods.dev/badge/skills/golemfoundation/octant-council-builder/evaluate.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.00010 | $0.02250 |
| Opus 5 | $0.00005 | $0.01125 |
| Sonnet 5 | $0.00002 | $0.00450 |
| Haiku 4.5 | $0.00001 | $0.00225 |
Grade A, and why
evaluate 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 10d 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Public Goods Evaluation Council
Orchestrate a multi-agent council to evaluate a public goods project. Three waves of agents gather data, evaluate from different lenses, and synthesize a final report.
Input
$ARGUMENTS is the project name or URL to evaluate.
If not provided, AskUserQuestion: "What project should the council evaluate?" with options for well-known projects or free text.
Store as $PROJECT. Derive $SLUG by lowercasing, replacing spaces/special chars with hyphens, truncating to 40 chars.
Step 1: Parse Input + Discover Agents
Discover the council roster dynamically from the filesystem:
Glob agents/data-*.md → $DATA_AGENTS
Glob agents/eval-*.md → $EVAL_AGENTS
Glob agents/synth-*.md → $SYNTH_AGENTS
For each agent file, read the frontmatter name and description fields.
Create the output directory:
mkdir -p council-out/$SLUG/data council-out/$SLUG/eval
Present the roster to the user:
AskUserQuestion:
question: "Council assembled. Proceed with evaluation?"
header: "Council"
options:
- label: "Run evaluation"
description: "Start the 3-wave evaluation"
preview: |
Project: $PROJECT
Wave 1 — Data Gathering ($N agents):
├─ [name]: [description]
├─ [name]: [description]
└─ ...
Wave 2 — Evaluation ($M agents):
├─ [name]: [description]
└─ ...
Wave 3 — Synthesis ($K agents):
└─ [name]: [description]
Output: council-out/$SLUG/REPORT.md
- label: "Modify roster"
description: "Add or remove agents before running"
If "Modify roster" → invoke the add-agent skill via the Skill tool, then re-discover.
Step 2: Create Team + All Tasks
TeamCreate(team_name="council-$SLUG", description="Public goods evaluation council for $PROJECT")
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.
- 10d ago First seen · 276 lines · 10 tokens per session scan A 054a904c1eda
evaluate is a skill published in the GitHub repository golemfoundation/octant-council-builder (3 stars, last pushed 5mo ago), licensed MIT. It adds 10 tokens to every session and 2,250 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…