Borrowing it
Nothing to install: this file belongs to Pattyboi101/indiestack. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Pattyboi101/indiestack/master/.claude/commands/meeting.mdgit clone --depth 1 https://github.com/Pattyboi101/indiestackWrote 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/commands/pattyboi101/indiestack/meeting)<a href="https://agentmods.dev/commands/pattyboi101/indiestack/meeting"><img src="https://agentmods.dev/badge/commands/pattyboi101/indiestack/meeting.svg" alt="Measured on agentmods" 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.00067 | $0.03534 |
| Opus 5 | $0.00034 | $0.01767 |
| Sonnet 5 | $0.00013 | $0.00707 |
| Haiku 4.5 | $0.00007 | $0.00353 |
Grade A, and why
meeting 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 8d 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 — 445 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meeting Skill
Run a real meeting — a state machine, not a survey. Agents diverge ideas, challenge each other, build on what survives, and stress test before anything becomes an action. The chair navigates phases, can skip optional ones, repeat phases still generating value, or loop back when a later phase reveals something that needs earlier work.
Detecting Intent
$ARGUMENTSisclose→ run Close Meeting$ARGUMENTSis empty → ask Patrick for the topic- Otherwise → run Start Meeting
Phase System
| Phase | Purpose | Mandatory? |
|---|---|---|
| Diverge | All ideas on the table — no criticism yet | Yes |
| Clarify | Surface assumptions, define terms, resolve ambiguity | Optional |
| Challenge | Push back, expose tensions, stress-test assumptions | Yes |
| Build | Develop the strongest ideas that survived Challenge | Yes |
| Stress Test | Attack the emerging consensus — try to break it | Yes |
| Converge | Find genuine agreement, surface remaining gaps | Optional |
| Decide | CEO resolves anything still genuinely unresolved | Only if unresolved |
Minimum required path: Diverge → Challenge → Build → Stress Test
[SATISFIED] and [CLOSE MEETING] flags are ignored until Stress Test completes. Collect them, note them, do not act on them.
Agent Flags
Agents write these in their responses to signal navigation needs:
| Flag | Meaning | Chair Action |
|---|---|---|
[NEEDS CLARIFY: X] |
X needs defining before I can contribute fully | Insert Clarify phase |
[BACK TO CHALLENGE: reason] |
Build surfaced a new tension that needs challenging | Loop to Challenge with the new tension |
[BACK TO BUILD: reason] |
Stress Test revealed a better approach worth developing | Loop to Build with refined idea |
[SATISFIED] |
Nothing more to add — happy with direction | Count; close if all satisfied (after Stress Test) |
[CLOSE MEETING: reason] |
CEO: meeting has run its course | Close immediately (only after Stress Test) |
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.
- 8d ago First seen · 445 lines · 67 tokens per session scan A 5f9b17ce1d5f
meeting is a command published in the GitHub repository Pattyboi101/indiestack (4 stars, last pushed 3mo ago), licensed MIT. It adds 67 tokens to every session and 3,534 once invoked, about $0.0003 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.