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.00991 |
| Opus 5.5 | $0.00036 | $0.00396 |
| Sonnet 5.5 | $0.00018 | $0.00198 |
| Haiku 4.5 | $0.00009 | $0.00099 |
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 24d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roleplay scenario builder
Give sellers a realistic opportunity to practise a specific behaviour, receive evidence-based feedback, and try it again.
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.
Weak scenario. 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.
Inputs
Reuse supplied context first. If a missing company fact would change the result, check the relevant sections of .enablement/context.md when available. Preserve source dates and approval limits.
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.
Supporting material
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.
Procedure
- 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. Set roles, timebox, reveal rules, observation, and debrief order. Choose coached practice or an unassisted observation round to suit the objective. Participants should know whether the facilitator may pause and coach; assessment conditions must follow the supplied standard.
- 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.
- Debrief and retry. Ask the participant what they noticed. Give evidence-based feedback on the target behaviour, then rerun the relevant moment. Compare attempts and agree where to apply the change in live work.
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.
- 24d ago Changed · +2 lines d0d11812fcb6
- 2mo 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 (16 stars, last pushed 25d ago), licensed MIT. It adds 90 tokens to every session and 991 once invoked, about $0.0004 per session on Opus 5.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.
roleplay-scenario-builder compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| roleplay-scenario-buildernthnclrk/enablement-skills | Skill | 16 | 25d ago | MIT | A | 90 | Codex |
| hr-onboardingnexu-io/open-design | Skill | 106k | yesterday | Apache-2.0 | A | 62 | Claude Code, Codex |
| book-mirrorgarrytan/gbrain | Skill | 32k | yesterday | MIT | A | 138 | Claude Code |
| exam-forecastanthropics/claude-for-legal | Skill | 9.9k | 3d ago | Apache-2.0 | A | 73 | Claude Code |
| lean-formalizewanshuiyin/Auto-claude-code-research-in-sleep | Skill | 19k | 3d ago | MIT | A | 81 | Claude Code |
| eli5companion-inc/feynman | Skill | 10k | 6d ago | MIT | A | 63 | Claude Code, Codex |
| deck-course-modulenexu-io/html-anything | Skill | 9.4k | 25d ago | Apache-2.0 | A | 25 | Claude Code, Codex |