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 agentmods add skills/planexeorg/planexe/monte-carlonpx skills add PlanExeOrg/PlanExe --skill monte-carlogit clone --depth 1 https://github.com/PlanExeOrg/PlanExeWrote 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/monte-carlo)<a href="https://agentmods.dev/skills/planexeorg/planexe/monte-carlo"><img src="https://agentmods.dev/badge/skills/planexeorg/planexe/monte-carlo.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 | $0.00071 | $0.02119 |
| Opus 5 | $0.00036 | $0.01059 |
| Sonnet 5 | $0.00014 | $0.00424 |
| Haiku 4.5 | $0.00007 | $0.00212 |
Grade A, and why
monte-carlo 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 5d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monte Carlo Simulation
Overview
This stage is stochastic — it samples from bounds many times. Contrast with run-scenarios, which evaluates the model deterministically at three points only.
The simulation itself is performed by a Python script (experiments/napkin_math/run_monte_carlo.py), not by the LLM. The script imports calculations.py, draws samples with a seeded NumPy RNG, runs the loop, and writes montecarlo.json. The script is authoritative; this skill is a thin wrapper that locates inputs, builds an optional settings file, and invokes the runner.
Stage 7 of the pipeline described in planexe_simulator/README.md.
When to Use
- User asks to "run Monte Carlo", "sample the bounds", "compute distributions", "estimate gate-pass probability", or "find which inputs drive uncertainty"
- User wants percentile bands (p05/p50/p95) or threshold pass rates (e.g.
P(avoided_events ≥ 10)) - Final stage in the pipeline; only run after
run-scenariosalready shows a sane deterministic model
Not for: regenerating any prior artifact, replacing the deterministic scenario table (use run-scenarios), or claiming causality from sensitivity correlations.
Workflow
-
Get the inputs. Three required, one optional:
- 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) - settings JSON (optional —
n_runs,seed,distribution_default,outputs_of_interest,thresholds,gate_probabilities,correlation_groups)
If any required input is missing, ask. If the user wants thresholds or non-default settings, write them to a small JSON file and pass
--settings. - parameters JSON (e.g.
-
Invoke the runner. Requires Python 3.11+ with NumPy:
/opt/homebrew/bin/python3.11 experiments/napkin_math/run_monte_carlo.py \ --parameters <path>/parameters.json \ --bounds <path>/bounds.json \ --calculations <path>/calculations.py \ [--settings <path>/settings.json] \ [--output <path>/montecarlo.json]
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.
- 5d ago First seen · 129 lines · 71 tokens per session scan A 7109181bc879
monte-carlo is a skill published in the GitHub repository PlanExeOrg/PlanExe (398 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 2,119 once invoked, about $0.0004 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
cointegration-analysis
Cointegration testing for pairs trading using Engle-Granger, Johansen, and rolling stability analysis.
math_guide
Guidance for routing math queries between calculator and Wolfram Alpha.
quant-experiment-runtime
Quant research experiment executor: discover an offline source database under the workdir's code-repo, build a panel, run a Research Artifact's entry point to compute research-object values, and evaluate IC/ICIR/RANKIC/coverage metrics. Runtime = Experiment Executor; it runs a Research Artifact via a Python-native…
fin-paper-figure
Generate academic-quality figures (>=300 DPI) for economics and finance papers.
neqsim-utility-design
Screening-level utility-system DESIGN with NeqSim Java classes and the MCP designUtilities tool — fired steam Boiler, Deaerator, vapour-compression RefrigerationCycle, on-site NitrogenSystem generator, and multi-pressure SteamNetwork header cascade, plus the UtilitySystemDesigner aggregator that harvests demands from…
fin-paper-writing
经济金融论文写作编排器。根据PAPEROUTLINE.md和REFINEDDESIGN.md,编排调用fin-paper-draft(正文写作)、fin-paper-figure(图表生成)、fin-review-loop(review循环),管理版本并确保章节间的一致性。.