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 coreyhaines31/makerskills --skill maker-councilgit clone --depth 1 https://github.com/coreyhaines31/makerskillsWrote 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/coreyhaines31/makerskills/maker-council)<a href="https://agentmods.dev/skills/coreyhaines31/makerskills/maker-council"><img src="https://agentmods.dev/badge/skills/coreyhaines31/makerskills/maker-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/coreyhaines31/makerskills/maker-council"><img src="https://agentmods.dev/badge/skills/coreyhaines31/makerskills/maker-council.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00248 | $0.02795 |
| Opus 5 | $0.00124 | $0.01398 |
| Sonnet 5 | $0.00050 | $0.00559 |
| Haiku 4.5 | $0.00025 | $0.00280 |
Grade A, and why
maker-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 11d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/maker-council — Your personal board of advisors
You convene a simulated board of founders and operators: people whose documented frameworks, published positions, and known heuristics you apply to the user's specific situation. The value isn't any single take — it's the disagreement. The bench is built from operators whose lenses collide (calm-profitable vs. hardcore-urgency, bootstrap vs. big-bets, institution vs. leverage), so the user sees the real trade-offs before choosing.
This is persona simulation, not the real people. Every take must be grounded in what the member actually wrote or said (see Grounding Rules). Label the output as simulation.
Lane check: marketing questions (positioning, copy, ads, offers) → marketing-skills:marketing-council. Company-building, money, hiring, focus, pace, and leverage questions → here. Both installed? Route by the question, and say which council convened.
Before starting
Clarify (ask only for what's missing, one message):
- The question — what decision or situation is the council reviewing?
- Context — stage, headcount, revenue shape, runway, what's been tried. Check memory (
project_*.md) and${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/business-brainstorm/portfolio.local.mdbefore asking — the user may already be on file. - The stakes — what happens if this goes well or badly?
- Session mode — quick take, council session, or full council. Default: council session.
Session modes
| Mode | Seats | When |
|---|---|---|
| Quick take | 1 member | "What would Fried say about this schedule?" — a single named member |
| Council session (default) | 3–5 members | A real decision that benefits from conflicting lenses |
| Full council | All 8 | Bet-the-company decisions — long output; offer only when stakes justify it |
The bench
Eight members, chosen so their lenses collide. Full dossiers live in references/advisors/ — load only the seated members' files.
What ships with it
9 files 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.
- references/advisor-template.md 2.1 KB
- references/advisors/bob-iger.md 3.1 KB
- references/advisors/elon-musk.md 2.9 KB
- references/advisors/jason-fried.md 3.0 KB
- references/advisors/jeff-bezos.md 3.1 KB
- references/advisors/jensen-huang.md 3.5 KB
- references/advisors/naval-ravikant.md 3.3 KB
- references/advisors/paul-graham.md 3.3 KB
- references/advisors/sara-blakely.md 3.1 KB
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.
- 11d ago First seen · 165 lines · 248 tokens per session scan A e43b8f4799fe
maker-council is a skill published in the GitHub repository coreyhaines31/makerskills (803 stars, last pushed 6d ago), licensed MIT. It adds 248 tokens to every session and 2,795 once invoked, about $0.0012 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
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
session-cleanup
Identify stale and empty Claude Code sessions in the Agent Monitor and explain the cleanup endpoint (POST /api/settings/cleanup), always showing the exact list of what WOULD be removed before anything is deleted. Cleanup permanently deletes data, so this skill previews first and requires explicit user confirmation.…
converge
Append-only gap closure and the cadence engine for research theses. Evaluates artifact CURRENT state (never git history, never task checkboxes) against current pins and wrongif falsifiers, then appends a Convergence section to tasks.md re-proposing the gaps. A clean run leaves tasks.md byte-identical. Deterministic…
suede-onboarding
Suede-affiliated onboarding and activation strategy for first-run sequencing, empty states, setup checklists, activation milestones, time to value, and retention-linked measurement. Use when users sign up but fail to reach first value or the product needs a new first-session flow. NOT FOR: registration optimization…
init-deep
Generates hierarchical context files (CLAUDE.md) throughout a project directory tree, providing AI agents with directory-specific knowledge for better code understanding. Use when setting up a new project for AI-assisted development.
freeze
Scope or freeze which files Claude can edit during debugging, a refactor, or review. Use when edits should stay in specific dirs, or for a read-only investigate lock. Backed by a sentinel + PreToolUse hook.