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.
git clone --depth 1 https://github.com/vstrapasson/rpg-marketplaceWrote 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/vstrapasson/rpg-marketplace/rpg-writers-room-help)<a href="https://agentmods.dev/commands/vstrapasson/rpg-marketplace/rpg-writers-room-help"><img src="https://agentmods.dev/badge/commands/vstrapasson/rpg-marketplace/rpg-writers-room-help/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/commands/vstrapasson/rpg-marketplace/rpg-writers-room-help"><img src="https://agentmods.dev/badge/commands/vstrapasson/rpg-marketplace/rpg-writers-room-help.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.00043 | $0.01749 |
| Opus 5 | $0.00022 | $0.00874 |
| Sonnet 5 | $0.00009 | $0.00350 |
| Haiku 4.5 | $0.00004 | $0.00175 |
Grade A, and why
rpg-writers-room-help 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 12d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Present this guide to the user conversationally — explain what the panel is for, what it needs, and what it will and will not do — then offer to scope a review (whole campaign, one arc, the last few sessions, or one aspect they are already worried about).
What it is for
You have built a campaign and run some of it. This kit convenes a writers' room — five expert critics, five deliberately different lenses — to tell you how to make it better. It reads two things and judges them separately: the artifacts in your Obsidian vault (is the writing good?) and the session transcripts (did you run it well?). Those are different questions with different evidence, and they come apart all the time — a beautiful dossier that never surfaced at the table, a thin note run brilliantly.
It is a critique layer. It never writes lore, never edits a vault note, and never gives you a score.
Quick start
- Install:
/plugin marketplace add ~/projects/rpg-marketplace, then/plugin install rpg-writers-room@rpg-marketplace, then/reload-plugins. - Run Claude Code from your vault root (the folder with
regioes/,npcs/,sessoes/, …). - Say
"avalie minha campanha"or"review my campaign". The scoping interview runs first — it will ask what to review, how wide, and what you already suspect is not working. - The report lands in
_criticas/critica-<campanha>-<data>.html. Open it in a browser.
What it needs
| Needed | Why |
|---|---|
| A campaign vault (guardian schema) | the artifacts under review |
campaign-bible-<slug>.md |
the yardstick — critics judge against the campaign's own declared truth, tone, and pillars, not a generic ideal |
sessoes/transcricoes/*.srt or *.txt |
the only evidence for conducting. .srt is better — timecodes make every citation checkable |
clue-map-<slug>.md (optional) |
lets the structural critic check the Three Clue Rule |
jogadores/ (optional) |
lets the player advocate judge spotlight balance per PC |
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.
- 12d ago First seen · 88 lines · 43 tokens per session scan A 2b08b18a2635
rpg-writers-room-help is a command published in the GitHub repository vstrapasson/rpg-marketplace (2 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 1,749 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-08-31.
Other commands, from other repositories
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
learn-story-flow
Learn story-flow concepts with interactive guidance for junior developers.
annex-a-deep-dive
Deep dive analysis of ISO 27001 Annex A control domains with implementation guidance.
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
start-13-4.en
Welcome to Lesson 13-4: Landing Page Implementation!
start-0-8
A Japanese-language command that displays the current project setup progress.