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 tt-a1i/matt-skills-with-to-goal --skill roundtablegit clone --depth 1 https://github.com/tt-a1i/matt-skills-with-to-goalWrote 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/tt-a1i/matt-skills-with-to-goal/roundtable)<a href="https://agentmods.dev/skills/tt-a1i/matt-skills-with-to-goal/roundtable"><img src="https://agentmods.dev/badge/skills/tt-a1i/matt-skills-with-to-goal/roundtable/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/tt-a1i/matt-skills-with-to-goal/roundtable"><img src="https://agentmods.dev/badge/skills/tt-a1i/matt-skills-with-to-goal/roundtable.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.00039 | $0.01019 |
| Opus 5 | $0.00019 | $0.00509 |
| Sonnet 5 | $0.00008 | $0.00204 |
| Haiku 4.5 | $0.00004 | $0.00102 |
Grade A, and why
roundtable 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 13d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pressure-test a decision, plan, or proposal by dispatching parallel sub-agents that argue it from deliberately opposed perspectives, then synthesising their debate into one verdict that preserves dissent.
Scope: decisions and designs only. Reviewing a diff is /code-review's job — don't point the roundtable at code changes.
Process
1. Frame the motion
Restate the user's question as a single debatable motion — a claim the table can support or oppose ("We should extract X into its own service"), not an open question ("What should we do about X?"). If the user's ask is too vague to frame, ask them to sharpen it first; if it's still fog, suggest running /grilling before convening the table.
Then assemble the evidence pack yourself, in the main thread: relevant file paths and excerpts, constraints, decisions already made, anything the user attached. Finding facts is the chair's job, not the seats' — sub-agents don't hunt on their own, so the whole table debates the same evidence.
Before dispatching anyone, confirm the motion is one sentence and the evidence pack is complete enough to argue from. A muddled motion should fail here — not inside four parallel sub-agents.
2. Seat the table
Default four seats:
- Skeptic — assumes the motion fails and argues why; enforces YAGNI; hunts hidden assumptions.
- Architect — argues from long-term structure: module depth, coupling, cost of evolution.
- User Advocate — argues from the experience of whoever uses or calls the result; real workflows over hypothetical ones.
- Pragmatist — argues from the shortest viable path: maintenance burden, opportunity cost, what ships this week.
The user may recompose the table for the topic ("seat a table of security experts") — keep it to 3–5 seats. Every seat brief, default or custom, must carry this line verbatim: "Your job is to make the strongest case from this perspective, even if your all-things-considered judgement would land elsewhere." That line is the first defence against convergence.
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.
- 13d ago First seen · 73 lines · 39 tokens per session scan A 6c35966375e2
roundtable is a skill published in the GitHub repository tt-a1i/matt-skills-with-to-goal (161 stars, last pushed 15d ago), licensed MIT. It adds 39 tokens to every session and 1,019 once invoked, about $0.0002 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
projectatlas
Use ProjectAtlas as the atlas-first orientation layer before broad source reads, with MCP-first task startup, short-alias worktree registration and routing, safe targeted initialization, ranked navigation, exact or federated graph evidence, purpose curation, health, lint, and repository-wide token reporting.
codex-coding-plugin
Build, review, or fix ProjectAtlas plugin/runtime installer integration for Codex, Claude Code, and OpenCode, especially version convergence, stale ProjectAtlas cache repair, MCP config generation, skill artifacts, host smoke tests, and fake-host tests for ProjectAtlas releases.
breaking-down-the-work
Splits scope into a product-first work breakdown that follows the 100% rule, keeps pieces from overlapping, uses outline numbers, and gives every piece a dictionary entry. Use when an epic, feature, or new subsystem needs a clean split into deliverables, or one source of truth before folders or work begin. Do not use…
staying-on-mission
Tests the current work against a written, lasting mission anchor and forces one choice, re-anchor, escalate, or stop. Use when an agent keeps finishing tasks but the work drifts from the goal, scope creeps, the same action repeats in a loop, or standards slip one small step at a time. Do not use for a tiny edit with…
closing-stale-packets
Brings an abandoned or half-filled change packet to an honest terminal state by completing it, closing it with a recorded rationale, or deleting it. Use when ng status flags a scaffold or invalid packet, a long session left a draft behind, or work was abandoned mid-packet. Do not use for an actively in-progress…
learning-from-experience
Turns incidents, near misses, bad handoffs, review surprises, escaped bugs, and signals from real use into lasting fixes to your safeguards. Use after something went wrong or nearly did and a future safeguard should change. Do not use during a live incident, which comes first, or to blame someone.