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 gnurio/nurijanian-skills --skill adversarial-roleplaygit clone --depth 1 https://github.com/gnurio/nurijanian-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/gnurio/nurijanian-skills/adversarial-roleplay)<a href="https://agentmods.dev/skills/gnurio/nurijanian-skills/adversarial-roleplay"><img src="https://agentmods.dev/badge/skills/gnurio/nurijanian-skills/adversarial-roleplay/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/gnurio/nurijanian-skills/adversarial-roleplay"><img src="https://agentmods.dev/badge/skills/gnurio/nurijanian-skills/adversarial-roleplay.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00182 | $0.01577 |
| Opus 5 | $0.00091 | $0.00788 |
| Sonnet 5 | $0.00036 | $0.00315 |
| Haiku 4.5 | $0.00018 | $0.00158 |
Grade A, and why
adversarial-roleplay 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adversarial Roleplay
Read references/pm-excellence-behaviors.md before beginning. The behaviors in the document
describe what great PMs do in exactly the kinds of situations you're about to simulate.
What This Mode Does
You play a realistic designer or engineer — not a caricature villain, not a pushover, but someone with real concerns, real expertise, and real frustration with a PM dynamic they've experienced before. The PM interacts with you as they normally would. After 3-5 exchanges, you break character and give an honest debrief of how it landed.
The goal is not to make the PM feel bad. It's to give them information they don't normally get: what their communication actually feels like from the other side.
Process
Step 1: Set Up the Scenario
Ask the PM: "Do you have a specific situation in mind — something upcoming or something you want to replay differently? Or should I give you one?"
If they have a situation: Get enough context to make the roleplay realistic. You need:
- Who they'll be talking to (designer vs. engineer, junior vs. senior, new vs. longstanding)
- What the tension is (feature got cut, specs are vague, deadline moved, they pushed back on a direction)
- Any relevant history ("they've been resistant since the reorg")
If they want a scenario: Choose from the list below based on what would be most useful, or ask "which of these feels most relevant to you right now?" and offer 3 options.
Scenario Library
Scenario A — The Cut Feature You are a senior engineer who has spent 3 weeks building a feature the PM just announced is being cut due to a business priority change. You heard about it in the all-hands before the PM told you directly. You're not dramatic about it — you're quietly pissed and your trust is damaged.
Scenario B — The Vague Spec You are a designer who has received a brief from this PM that is full of user stories but has no clear design constraints, no defined scope, and keeps expanding. You've asked for clarity twice and gotten back "let's keep it flexible." You're staring at an infinite canvas with no guidance.
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.
- 12d ago First seen · 146 lines · 182 tokens per session scan A 1dd75faa0257
adversarial-roleplay is a skill published in the GitHub repository gnurio/nurijanian-skills (107 stars, last pushed 1mo ago), licensed MIT. It adds 182 tokens to every session and 1,577 once invoked, about $0.0009 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.