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 nthnclrk/enablement-skills --skill roleplay-scenario-buildergit clone --depth 1 https://github.com/nthnclrk/enablement-skillsWrote 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/nthnclrk/enablement-skills/roleplay-scenario-builder)<a href="https://agentmods.dev/skills/nthnclrk/enablement-skills/roleplay-scenario-builder"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/roleplay-scenario-builder/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/skills/nthnclrk/enablement-skills/roleplay-scenario-builder"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/roleplay-scenario-builder.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.00090 | $0.00891 |
| Opus 5 | $0.00045 | $0.00445 |
| Sonnet 5 | $0.00018 | $0.00178 |
| Haiku 4.5 | $0.00009 | $0.00089 |
Grade A, and why
roleplay-scenario-builder 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 11d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roleplay scenario builder
Build a drill that changes one selling behavior. If it plays like theater, rewrite it.
A scenario tests one behavior under one pressure. A recorded-call review is call-review-coach. A pass/fail gate is certification-program-builder.
Practice. Participant sees: "VP Ops, 12 minutes, they already have a process." Facilitator holds: they will not name the cost until you ask who owns the escalation. Score: did the rep diagnose before pitching.
Theater. A four-page buyer bio, a memorized script, and "be more consultative" as the score.
If the participant can succeed by performing confidence instead of the target behavior, it is not a drill.
Confirm Inputs First
Ask only for the inputs that change the drill:
- Who is practicing, and which one behavior must change
- Segment, persona, and stage
- Difficulty: baseline, stretch, or advanced
- Timebox, participant count, and who facilitates
- Whether a pass threshold already exists. If the result controls readiness, route the standard to
certification-program-builder
Label fictional company and buyer details as invented. Do not present them as real customers, competitors, or proof.
Read The Right Reference
Read references/roleplay-scenario-framework.md for tension design, reveal rules, and worked pass/fail excerpts. Skip it if the user already has a scenario and only wants the scorecard or run protocol.
Default Workflow
- Name the behavior and the evidence that would prove it. Separate a critical failure from a coachable miss. Done when a facilitator can see the behavior without inferring mindset.
- Build one focused scenario. Add a progression only when asked, changing one difficulty variable at a time.
- Ground it in field evidence when you have it. Anonymize. Invented details stay labeled.
- Split the briefs. Participant sees what a seller would reasonably know. Facilitator holds hidden blockers, reveal conditions, anchors, and escalation cues. Done when nothing in the participant brief gives away the test.
- Write the pressure the behavior has to survive. One unexpected turn. Buyer responses follow what the seller does, not a memorized dialogue.
- Write the run protocol. Roles, timebox, reveal rules, pause or retry, observation, debrief order. Run without coaching unless the pause condition hits.
- Anchor the score to visible behavior. Cite what happened. Use a supplied pass rule; do not invent one. In a certification, supply only the scenario and evidence prompts.
- End with one retry. Participant self-assesses first. Facilitator names one behavior to run again.
What ships with it
2 files 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.
- 11d ago First seen · 76 lines · 90 tokens per session scan A de8b1b3cac07
roleplay-scenario-builder is a skill published in the GitHub repository nthnclrk/enablement-skills (13 stars, last pushed 22d ago), licensed MIT. It adds 90 tokens to every session and 891 once invoked, about $0.0005 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-30.
Other skills, from other repositories
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
book-mirror
Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…
miniapp
Build a tiny interactive HTML playground only when someone asks to see, play with, or step through a mechanism.
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
deck-course-module
A course or workshop slide template with persistent learning goals, teaching pages, multiple-choice self-tests, and a wrap-up.
master-yinguang
A reference-based assistant for questions about Yinguang and Pure Land Buddhism, a Buddhist tradition focused on faith, ethical living, and practice connected with rebirth in the Pure Land. It can answer in Yinguang’s historical teaching style.