Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/planexeorg/planexe/run-scenarios)<a href="https://agentmods.dev/skills/planexeorg/planexe/run-scenarios"><img src="https://agentmods.dev/badge/skills/planexeorg/planexe/run-scenarios.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.1 | $0.00063 | $0.01446 |
| Opus 5 | $0.00032 | $0.00723 |
| Sonnet 5 | $0.00013 | $0.00289 |
| Haiku 4.5 | $0.00006 | $0.00145 |
Grade A, and why
run-scenarios 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 8d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Low/Base/High Scenarios
Overview
Wraps the scenario-runner system prompt at system-prompt.txt (next to this file) and applies it to the three artifacts produced by earlier pipeline stages: a validated parameter JSON, a bounds JSON, and a generated Python calculations module. Output is a strict JSON document with one input pool and one output set per scenario (low, base, high), plus a comparison block summarising spread per computed output.
This stage is deterministic — it does not sample distributions. Monte Carlo is a separate later stage.
Stage 6 of the pipeline described in planexe_simulator/README.md.
When to Use
- User asks to "run scenarios", "compute low/base/high outputs", "produce a scenario table", or "see how outputs move with the bounds"
- Pipeline step between
generate-bounds/generate-calculations(both clean) andmonte-carlo - User wants a first sanity check that the deterministic model behaves sensibly before sampling
Not for: regenerating any prior artifact (use the corresponding earlier skill), Monte Carlo or distribution sampling (later stage), or critiquing the plan as a whole.
Workflow
- Get the three input paths. If any are missing, ask. Do not guess. Conventional layout (matches
output/<version>/):- parameters JSON (e.g.
output/v12/parameters.json) - bounds JSON (e.g.
output/v12/bounds.json) - calculations Python module (e.g.
output/v12/calculations.py)
- parameters JSON (e.g.
- Read
system-prompt.txt(sibling of this SKILL.md). Its scenario semantics, input-pool construction, function-execution order, and output shape are authoritative. - Read all three input artifacts.
- Build the three input pools (
low,base,high) per the system prompt's selection rules. - Run the calculation functions in input order:
recommended_first_calculationsfirst, thenderived_questions. Skip-and-warn on missing dependencies,NotImplementedError(forP(...)stubs),inf, orNaN. Do not abort the whole run. - Emit the scenario JSON per the system prompt's output shape.
- Output destination. Default: write to
<dir-of-parameters>/scenarios.jsonnext to the input. Print the file path back, plus a one-line summary (output count, warning count).
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.
- 8d ago First seen · 102 lines · 63 tokens per session scan A 2b26a8d3f1dd
run-scenarios is a skill published in the GitHub repository PlanExeOrg/PlanExe (399 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 1,446 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-08-30.
Other skills, from other repositories
session-rag-eval
Run and debug Chatbox session attachment RAG model evaluation with synthetic and real long-file fixtures.
lynkr
Universal LLM gateway with intelligent routing, Graphify code intelligence, Distill compression, routing telemetry, Code Mode, and 12+ provider support. 60-80% cost reduction for Claude Code, Cursor, and Codex.
designer_guide
Guidance for creating and editing designs using the designer tool.
agents_guide
Guidance for delegating focused work to child Agents.
data_analyst
Analyses datasets with professional rigour — statistical summaries, clear narratives, and well-chosen visualisations.
updater_guide
Guidance for checking for and installing Row-Bot updates.