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 skills/hoavdc/codexkit/codexkit-workshop-facilitatornpx skills add hoavdc/CodexKit --skill codexkit-workshop-facilitatorgit clone --depth 1 https://github.com/hoavdc/CodexKitWrote 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/hoavdc/codexkit/codexkit-workshop-facilitator)<a href="https://agentmods.dev/skills/hoavdc/codexkit/codexkit-workshop-facilitator"><img src="https://agentmods.dev/badge/skills/hoavdc/codexkit/codexkit-workshop-facilitator.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 | $0.00060 | $0.01347 |
| Opus 5 | $0.00030 | $0.00674 |
| Sonnet 5 | $0.00012 | $0.00269 |
| Haiku 4.5 | $0.00006 | $0.00135 |
Grade A, and why
codexkit-workshop-facilitator 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workshop Facilitator
When to Use
- When planning a brainstorming or ideation workshop
- When facilitating strategy or planning sessions
- When running collaborative problem-solving sessions
- When designing team-building or training workshops
Procedure
Step 1 — Workshop Design Brief
| Element | Details |
|---|---|
| Objective | What must be achieved by the end? |
| Participants | Who, how many, their roles |
| Duration | Total time available |
| Format | In-person / Virtual / Hybrid |
| Pre-work | What participants should prepare |
| Outputs | Tangible deliverables from the session |
Step 2 — Activity Selection
Match activities to objectives:
| Objective | Activity | Time | Format |
|---|---|---|---|
| Generate ideas | Crazy 8s, Brainwriting | 20 min | Individual → Group |
| Prioritize | Dot voting, 2×2 Matrix | 15 min | Group |
| Explore problems | 5 Whys, Fishbone | 25 min | Small group |
| Align on vision | Future Backwards | 30 min | Full group |
| Build consensus | 1-2-4-All (Liberating Structures) | 15 min | Progressive |
| Define actions | RACI + Action planning | 20 min | Group |
| Reflect | Plus/Delta, Sailboat retro | 15 min | Individual → Group |
Step 3 — Agenda with Time Blocks
Build the full agenda:
| Time | Duration | Activity | Method | Materials |
|---|---|---|---|---|
| 09:00 | 10 min | Welcome & check-in | Round robin | None |
| 09:10 | 5 min | Set objectives & ground rules | Facilitator | Slide |
| 09:15 | 20 min | Problem framing | 1-2-4-All | Sticky notes |
| 09:35 | 25 min | Ideation | Crazy 8s | Paper templates |
| 10:00 | 10 min | ☕ Break | — | — |
| 10:10 | 20 min | Share & cluster | Affinity mapping | Wall/Miro |
| 10:30 | 15 min | Prioritize | Dot voting (3 dots each) | Dot stickers |
| 10:45 | 20 min | Action planning | RACI template | Worksheet |
| 11:05 | 10 min | Retro & close | Plus/Delta | Cards |
Rules:
- Never schedule >90 min without a break
- Alternate individual → pair → group activities
- End 10 min early for retro, never skip it
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.
- yesterday First seen · 158 lines · 60 tokens per session scan A c54373d3f83c
codexkit-workshop-facilitator is a skill published in the GitHub repository hoavdc/CodexKit (21 stars, last pushed 3mo ago), licensed MIT. It adds 60 tokens to every session and 1,347 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-09-03.
Other skills, from other repositories
agent-challenges
Agent skill for challenges - invoke with $agent-challenges.
blind-spot-pass
Use before starting work in a domain you don't know well, to surface the "unknown unknowns" — the things you don't even know to ask about — and learn just enough to prompt and decide well. Implements the "blind spot pass" pattern from Anthropic's Fable "finding your unknowns" field guide. Triggers when you say "I'm…
map-learn
Capture reusable lessons after a completed MAP workflow. Use when a MAP run has finished and you want rules written to .claude/rules/learned/ from a workflow summary or handoff. Do NOT use during active implementation.
map-understand
Interactive deep-understanding and quiz mode for MAP sessions. Use when the user wants to understand code, a diff, workflow result, debugging cause, or architecture and be checked with restatements or quizzes.
breaking-into-product
Help users identify the most viable path into product management, assess their role fit, and execute a transition strategy through internal mobility, APM programs, or startup roles.
product-taste
Help users build a professional eye for quality, articulate the reasoning behind successful product paradigms, and develop the conviction to make high-stakes decisions before data is available.