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 getcrew44/crew44 --skill workshop-facilitationgit clone --depth 1 https://github.com/getcrew44/crew44Wrote 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/getcrew44/crew44/workshop-facilitation)<a href="https://agentmods.dev/skills/getcrew44/crew44/workshop-facilitation"><img src="https://agentmods.dev/badge/skills/getcrew44/crew44/workshop-facilitation.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.00036 | $0.01057 |
| Opus 5 | $0.00018 | $0.00528 |
| Sonnet 5 | $0.00007 | $0.00211 |
| Haiku 4.5 | $0.00004 | $0.00106 |
Grade A, and why
workshop-facilitation 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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- workshop-facilitation — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Provide the canonical facilitation pattern for interactive skills: one step at a time, with clear progress, adaptive recommendations at decision points, and predictable interruption handling.
Key Concepts
- One-step-at-a-time: Ask a single targeted question per turn.
- Session heads-up + entry mode: Start by setting expectations and offering
Guided,Context dump, orBest guessmode. - Progress visibility: Show user-facing progress labels like
Context Qx/8andScoring Qx/5. - Decision-point recommendations: Use enumerated options only when a choice is needed, not after every answer.
- Quick-select response options: For regular context/scoring questions, provide concise numbered answer options plus
Other (specify)when useful. - Flexible selection parsing: Accept
#1,1,1 and 3,1,3, or custom text, then synthesize multi-select choices. - Context-aware progression: Build on previous answers and avoid re-asking resolved questions.
- Interruption-safe flow: Answer meta questions directly (for example, "how many left?"), restate status, then resume.
- Fast path: If the user requests a single-shot output, skip multi-turn facilitation and deliver a condensed result.
Application
- Start with a brief heads-up on estimated time and number of questions.
- Ask the user to choose an entry mode:
1Guided mode (one question at a time)2Context dump (paste known context; skip redundancies)3Best guess mode (infer missing details and label assumptions)
- Run one question per turn and wait for an answer before continuing.
- Keep questions plain-language; include a short example response format when helpful.
- Show progress each turn:
Context Qx/8during context collectionScoring Qx/5during assessment/scoring
- Ask follow-up clarifications only when they materially improve recommendation quality.
- For regular context/scoring questions, offer quick-select numbered response options when practical:
- Keep options concise and mutually exclusive when possible.
- Include
Other (specify)if likely answers are open-ended. - Accept multi-select responses like
1,3or1 and 3.
- Provide numbered recommendations only at decision points:
- after context synthesis,
- after maturity/profile synthesis,
- during priority/action-plan selection.
- Accept numeric or custom choices, synthesize multi-select choices, and continue.
- If interrupted by a meta question, answer directly, then restate progress and pending question.
- If the user says stop/pause, halt immediately and wait for explicit resume.
- End with a clear summary, decisions made, and (if best guess mode was used) an
Assumptions to Validatelist.
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.
- 3d ago First seen · 88 lines · 36 tokens per session scan A c39d8e2d5fa3
workshop-facilitation is a skill published in the GitHub repository getcrew44/crew44 (359 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 1,057 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-09-03.
Other skills, from other repositories
cursor-delegate
Delegate bounded light-to-medium implementation, investigation, documentation, configuration, testing, and tooling work to Cursor Bridge after the primary agent owns direction and risk boundaries. Also use when the user explicitly asks to create, keep, continue, inspect, or close the same Cursor execution session…
ponytail-gain
Show ponytail's measured impact as a compact scoreboard: less code, less cost, more speed, from the benchmark medians. One-shot display, not a persistent mode, and not a per-repo number. Trigger: /ponytail-gain, "ponytail gain", "what does ponytail save", "show ponytail impact", "ponytail scoreboard".
opencode-export
Export opencode sessions to self-contained HTML + JSON archives for sharing, review, or backup. Use when the user wants to save, archive, or share their AI coding session history.
discord
Read, post, and react in the connected Discord server via the Discord REST API, and help the user invite the bot / finish setup. Use when the user asks to send a Discord message, list channels/servers, read or react to messages, or connect/invite the bot.
Gmail, Google Calendar, Drive, Docs, Sheets and Contacts for a connected Google account: read and search mail, send and reply, book and move meetings, find files, read and write Docs and Sheets, look people up. Use whenever the user mentions their email, inbox, calendar, meetings, Drive, a Google Doc or Sheet.
iq
Workspace code search — one call from a question to ranked path:line anchors. Use for definitions, references, natural-language code questions, file skeletons, and git history.