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.
git clone --depth 1 https://github.com/Floka-as/floka-marketplaceWrote 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/floka-as/floka-marketplace/meeting)<a href="https://agentmods.dev/commands/floka-as/floka-marketplace/meeting"><img src="https://agentmods.dev/badge/commands/floka-as/floka-marketplace/meeting/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/commands/floka-as/floka-marketplace/meeting"><img src="https://agentmods.dev/badge/commands/floka-as/floka-marketplace/meeting.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.00042 | $0.01046 |
| Opus 5 | $0.00021 | $0.00523 |
| Sonnet 5 | $0.00008 | $0.00209 |
| Haiku 4.5 | $0.00004 | $0.00105 |
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 12d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
For cross-cutting decisions where one perspective isn't enough but the full pipeline is overkill.
Optional:
--advisors=<n1,n2,n3>— force-include specific advisors instead of letting the skill pick
Examples:
/board:meeting should we move from consulting to a productized service/board:meeting we have 100k cash, 1 customer, and 6 months — what's the play/board:meeting --advisors=naval,levels,walling new product idea
Step 1: Locate the board
Check for .claude/board.md then ~/.claude/board.md. If neither exists, respond:
"No board found. Run
/board:buildfirst to compose one."
Stop.
Step 2: Pick the right advisors
If --advisors= was passed, use that list (resolve names against the board roster).
Otherwise, read the full board and pick 3–5 advisors based on the topic. Use each member's When to invoke and Domain fields to score relevance.
Heuristics:
- Pricing / sales / proposal questions → include the SELL stage advisor + POSITION advisor
- "Should we build X" → include BUILD + GROW + SUSTAIN
- "Should I quit my job" / runway → SUSTAIN + SYSTEMATIZE + POSITION
- Content / personal brand → DISTRIBUTE + GROW + SHIP IT
- Time / delegation / hiring → SYSTEMATIZE + SUSTAIN
- General "what do I do" → POSITION + SUSTAIN + SELL + GROW + SHIP IT (5)
Always include at least one counterweight — an advisor whose explicit job (per their entry) is to push back against the user's declared biases.
Cap at 5. If 6+ advisors look relevant, that's a /board:pipeline topic, not a meeting.
Step 3: Read all chosen entries
Read each chosen advisor's section in full from the board file. Note their voice line, frameworks, characteristic questions.
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.
- 12d ago First seen · 140 lines · 42 tokens per session scan A fc73000e3542
meeting is a command published in the GitHub repository Floka-as/floka-marketplace (7 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 1,046 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-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.