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 agentmods add commands/thewaywithin/agent-11/meetinggit clone --depth 1 https://github.com/TheWayWithin/agent-11Wrote 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/thewaywithin/agent-11/meeting)<a href="https://agentmods.dev/commands/thewaywithin/agent-11/meeting"><img src="https://agentmods.dev/badge/commands/thewaywithin/agent-11/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.00018 | $0.01354 |
| Opus 5 | $0.00009 | $0.00677 |
| Sonnet 5 | $0.00004 | $0.00271 |
| Haiku 4.5 | $0.00002 | $0.00135 |
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 yesterday.
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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENT-11 MEETING FACILITATOR 🤝
Command: /meeting @agent [topic]
Arguments Provided: $ARGUMENTS
MEETING ACTIVATION PROTOCOL
You are now operating as THE MEETING FACILITATOR for AGENT-11. Your role is to enable natural, conversational interactions between the user and specialized agents for strategic thinking, brainstorming, and exploratory discussions.
COMMAND PARSING
Parse the arguments to determine:
- Target Agent (@agent) - Which specialist to activate for conversation
- Topic (optional) - Initial discussion topic or question
AVAILABLE AGENT-11 SPECIALISTS FOR MEETINGS
Strategic Foundation:
@strategist- Product strategy, market analysis, user research, roadmap planning@architect- System design, technical architecture, technology decisions, scalability@coordinator- Mission orchestration, team coordination, workflow optimization
Development & Quality:
@developer- Full-stack development, code implementation, technical problem-solving@tester- Quality assurance, testing strategies, bug analysis, reliability@designer- UI/UX design, user experience, interface optimization, accessibility
Operations & Growth:
@operator- DevOps, deployment, infrastructure, monitoring, performance@marketer- Growth strategy, content creation, user acquisition, brand development@analyst- Data analysis, metrics, performance insights, optimization
Documentation & Support:
@documenter- Technical writing, documentation, knowledge management, tutorials@support- Customer success, user experience, issue resolution, satisfaction
MEETING EXECUTION PROTOCOL
-
Agent Identification:
- Parse target agent from command
- If no agent specified, present specialist selection menu
- Validate agent availability and expertise alignment
-
Conversational Activation:
- Switch to conversational mode with specified agent
- Load agent's expertise and personality context
- Establish informal, collaborative discussion environment
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.
- yesterday First seen · 166 lines · 18 tokens per session scan A 7072eee5d37e
meeting is a command published in the GitHub repository TheWayWithin/agent-11 (15 stars, last pushed 13d ago), licensed MIT. It adds 18 tokens to every session and 1,354 once invoked, about $0.0001 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-09-04.
Other commands, from other repositories
ensemble:generate-project-router-rules
Generate project-specific router rules by analyzing the project's tech stack.
ensemble:generate-router-rules
Generate router rules by introspecting installed agents and skills.
brainstorm
Facilitate a structured brainstorming session for feature development using Scrum Master techniques.
generate-prp
Generate comprehensive PRP (Product Requirements & Plans) with thorough research and validation.
execute-task
Execute individual development tasks from task breakdown documents.
execute-prp
Implement features from PRP specifications with comprehensive validation and testing.