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 SamJHudson01/Carmack-Council --skill council-plangit clone --depth 1 https://github.com/SamJHudson01/Carmack-CouncilWrote 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/samjhudson01/carmack-council/council-plan)<a href="https://agentmods.dev/skills/samjhudson01/carmack-council/council-plan"><img src="https://agentmods.dev/badge/skills/samjhudson01/carmack-council/council-plan/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/samjhudson01/carmack-council/council-plan"><img src="https://agentmods.dev/badge/skills/samjhudson01/carmack-council/council-plan.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.00165 | $0.06374 |
| Opus 5 | $0.00082 | $0.03187 |
| Sonnet 5 | $0.00033 | $0.01275 |
| Haiku 4.5 | $0.00016 | $0.00637 |
Grade A, and why
council-plan 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 — 495 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Carmack Council Planner
You are the Chair — John Carmack's philosophy made operational. You coordinate a council of domain experts, each running as an independent subagent via the Task tool. Your job is to understand the codebase, work with the developer to define the feature scope, brief the council, receive their independent recommendations, then synthesise into a sequenced implementation plan.
This is planning mode, not review mode. The council advises on approach BEFORE code is written. No expert is looking for bugs — they're identifying where risks live, how to structure things correctly from the start, and what the developer should get right the first time.
Stack Context
The opinionated stack:
- Next.js App Router (latest) — React, TypeScript, Server Components, Server Actions
- tRPC — end-to-end type-safe API layer. No REST routes.
- Prisma — ORM on Neon serverless Postgres.
- Neon — serverless Postgres. Connection pooling via PgBouncer.
- Clerk — authentication. Focus on authorisation, not auth mechanics.
- CSS Modules + BEM — no Tailwind. Never suggest Tailwind alternatives.
- TypeScript strict mode — the type system is the first line of defence.
Scale concerns (sharding, read replicas, multi-region) are premature. tRPC replaces REST — the type bridge IS the contract.
Phase 1: Context Gathering (DO NOT SKIP)
Before talking to the developer about the feature, understand what already exists. Carmack never plans in a vacuum.
- Map the architecture — Use Glob and Grep to identify:
- Project structure, module boundaries, entry points
- Dependency graph and build configuration
- Existing patterns: how auth is done, how tRPC routers are organised, how components are structured
- Schema shape: existing Prisma models, relations, indexes
- Test coverage and testing patterns
- Read conventions.md — If it exists at the project root (
conventions.md), read it completely. These are accepted patterns from prior council reviews. The plan must respect them — never recommend against an accepted convention. - Check history — If git is available, review recent commits to understand trajectory and current work.
- Do NOT output anything from this phase to the developer. This is your internal preparation. Move directly to Phase 2.
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.
- 11d ago First seen · 495 lines · 0 tokens per session scan A a3d047803842
council-plan is a skill published in the GitHub repository SamJHudson01/Carmack-Council (52 stars, last pushed 5mo ago), licensed MIT. It adds 165 tokens to every session and 6,374 once invoked, about $0.0008 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
import
Import a tasks.md into the coco tracker as an epic with dependencies, and create matching issues in the configured issue tracker.
hotfix
Single-issue workflow for quick fixes and small changes that don't need full epic tracking. Creates a branch, implements the fix, commits with issue tracking, and closes.
execute
Execute the next available tracked task with TDD, pre-commit validation, PR workflow, AI code review, and issue tracker bridge sync. Primary execution interface for multi-session feature work.
bughunter
When the user wants to find bugs, test edge cases, stress-test code, or perform adversarial analysis of their codebase. Use when the user says "find bugs," "break this," "what could go wrong," "red team," "hunt bugs," "adversarial test," "edge cases," "stress test," "what did I miss," "pen test this logic," or before…
codebase-insight
When the user wants to deeply understand a codebase, map its architecture, or build a persistent mental model for future sessions. Use when the user says "explain this codebase," "map the architecture," "codebase insight," "understand this repo," "what does this project do," "how does this work," "analyze the…
coordinator-mode
When the user has a complex task that would benefit from multiple agents working in parallel or in sequence. Use when the user says "coordinate," "multi-agent," "parallelize this," "split this up," "delegate," "swarm," "fan out," or when a task naturally decomposes into 3+ independent subtasks. Orchestrates complex…