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 beel-collab/presets.dev --skill monte-carlo-monitor-creationgit clone --depth 1 https://github.com/beel-collab/presets.devWrote 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/beel-collab/presets.dev/monte-carlo-monitor-creation)<a href="https://agentmods.dev/skills/beel-collab/presets.dev/monte-carlo-monitor-creation"><img src="https://agentmods.dev/badge/skills/beel-collab/presets.dev/monte-carlo-monitor-creation/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/beel-collab/presets.dev/monte-carlo-monitor-creation"><img src="https://agentmods.dev/badge/skills/beel-collab/presets.dev/monte-carlo-monitor-creation.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.00021 | $0.02462 |
| Opus 5 | $0.00010 | $0.01231 |
| Sonnet 5 | $0.00004 | $0.00492 |
| Haiku 4.5 | $0.00002 | $0.00246 |
Grade A, and why
monte-carlo-monitor-creation 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monte Carlo Monitor Creation Skill
This skill teaches you to create Monte Carlo monitors correctly via MCP. Every creation tool runs in dry-run mode and returns monitors-as-code (MaC) YAML. No monitors are created directly -- the user applies the YAML via the Monte Carlo CLI or CI/CD.
Reference files live next to this skill file. Use the Read tool (not MCP resources) to access them:
- Metric monitor details:
references/metric-monitor.md(relative to this file) - Validation monitor details:
references/validation-monitor.md(relative to this file) - Custom SQL monitor details:
references/custom-sql-monitor.md(relative to this file) - Comparison monitor details:
references/comparison-monitor.md(relative to this file) - Table monitor details:
references/table-monitor.md(relative to this file)
When to activate this skill
Activate when the user:
- Asks to create, add, or set up a monitor (e.g. "add a monitor for...", "create a freshness check on...", "set up validation for...")
- Mentions monitoring a specific table, field, or metric
- Wants to check data quality rules or enforce data contracts
- Asks about monitoring options for a table or dataset
- Requests monitors-as-code YAML generation
- Wants to add monitoring after new transformation logic (when the prevent skill is not active)
When NOT to activate this skill
Do not activate when the user is:
- Just querying data or exploring table contents
- Triaging or responding to active alerts (use the prevent skill's Workflow 3)
- Running impact assessments before code changes (use the prevent skill's Workflow 4)
- Asking about existing monitor configuration (use
getMonitorsdirectly) - Editing or deleting existing monitors
Available MCP tools
All tools are available via the monte-carlo MCP server.
| Tool | Purpose |
|---|---|
testConnection |
Verify auth and connectivity before starting |
search |
Find tables/assets by name; use include_fields for columns |
getTable |
Schema, stats, metadata, domain membership, capabilities |
getValidationPredicates |
List available validation rule types for a warehouse |
getDomains |
List MC domains (only needed if table has no domain info) |
createMetricMonitorMac |
Generate metric monitor YAML (dry-run) |
createValidationMonitorMac |
Generate validation monitor YAML (dry-run) |
createComparisonMonitorMac |
Generate comparison monitor YAML (dry-run) |
createCustomSqlMonitorMac |
Generate custom SQL monitor YAML (dry-run) |
createTableMonitorMac |
Generate table monitor YAML (dry-run) |
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 · 223 lines · 21 tokens per session scan A 62cf7e39af16
monte-carlo-monitor-creation is a skill published in the GitHub repository beel-collab/presets.dev (3 stars, last pushed 4mo ago), licensed MIT. It adds 21 tokens to every session and 2,462 once invoked, about $0.0001 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 skills, from other repositories
skill-creator-primer
You MUST load this skill before the skill-creator skill AND before making ANY change to, or conducting a review of ANY Agent Skill. Triggers include creating, editing, reviewing, or contributing to any part of an Agent Skill (description, frontmatter, body, references, scripts, trigger evals, conflicts, etc).
llm-wiki
Use when building or maintaining a self-contained personal knowledge base (an LLM wiki) in plain markdown. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki health, auditing article claims against their sources, critiquing a wiki source's reasoning, superseding stale knowledge, 'add to…
extract-wisdom
Extract wisdom, insights, and actionable takeaways from YouTube videos, blog posts, articles, or text files. Use when asked to extract wisdom or key insights from a given content source.
apply-mantel-styles
Provides guidelines for applying Mantel's brand styles to diagrams and frontend components. Use when asked to create visuals that need to align with Mantel's branding.
home-assistant
This skill should be used when helping with Home Assistant setup, including creating automations, modifying dashboards, checking entity states, debugging automations, and managing the smart home configuration. Use this for queries about HA entities, YAML automation/dashboard generation, or troubleshooting HA issues.
aws-strands-agents-agentcore
Use when working with AWS Strands Agents SDK or Amazon Bedrock AgentCore platform for building AI agents. Provides architecture guidance, implementation patterns, deployment strategies, observability, quality evaluations, multi-agent orchestration, and MCP server integration.