Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add JMMonte/agentic-digital-twin/plugin install agentic-digital-twinWrote 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/jmmonte/agentic-digital-twin/guardrails-check)<a href="https://agentmods.dev/skills/jmmonte/agentic-digital-twin/guardrails-check"><img src="https://agentmods.dev/badge/skills/jmmonte/agentic-digital-twin/guardrails-check/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/jmmonte/agentic-digital-twin/guardrails-check"><img src="https://agentmods.dev/badge/skills/jmmonte/agentic-digital-twin/guardrails-check.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.00091 | $0.00919 |
| Opus 5 | $0.00046 | $0.00460 |
| Sonnet 5 | $0.00018 | $0.00184 |
| Haiku 4.5 | $0.00009 | $0.00092 |
Grade A, and why
guardrails-check 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 10d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guardrails check (and how to grow the checklist)
The meta-rule: a result that "ran clean" is not a result that is
correct. Voxel kernels, CFD configs, and np.interp fail SILENTLY — no
exception to catch — which is the worst failure mode for an agent. Every
derived number must agree with an independent anchor before you trust it.
The full, living checklist is ${CLAUDE_PLUGIN_ROOT}/GUARDRAILS.md (and the
project-local copy at <project>/GUARDRAILS.md after scaffolding). Read it.
This skill is the workflow for using it and keeping it current.
Before declaring ANY result correct, sweep these
- Wrong boolean, clean mesh. A failed subtract / flood-filled cavity / no-op union still yields a watertight, positive-volume mesh. Did an audit assert the EXPECTED bbox/volume/CG, not just ">0"?
np.interpdirection. Any value→score map: isxpascending? Is lower-is-better done with ascendingxp+ REVERSEDfp? Hand-check a value at each end of the band.- Anchor cross-check. Is every derived number checked against a
[PUB]value, an analytic formula, or the REAL exported artifact — not an assumed envelope? - Voxel/CAD silence. Union first, subtract last, vent every cavity? No
voxel artifact on the outer mold line (sub-voxel wall reads as closed)?
Loft
ruled=pinned? - CFD config.
FLUID_MODELset explicitly (ideal-gas trap)? Validated against an analytic anchor and a grid-convergence study? - Sim signs + indices. Every control-derivative sign written down and self-checked at runtime? State-vector slices named (the v-vs-w trap)? Subsystems calibrated open-loop before closing the loop?
- rerun.
rr.save()before opening the viewer (it REPLACES the sink)?vertex_normalson everyMesh3D? Milestone archived toout/history/<date>/before regenerating? - Mesh hygiene. Decimated before queries? Degenerate faces cleaned
(
update_faces(nondegenerate_faces()),np.nanmax)? - Look at it. Did you open the render — including the underside and the region you touched?
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.
- 10d ago First seen · 72 lines · 91 tokens per session scan A d70012b30528
guardrails-check is a skill published in the GitHub repository JMMonte/agentic-digital-twin (2 stars, last pushed 2mo ago), licensed MIT. It adds 91 tokens to every session and 919 once invoked, about $0.0005 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
jetson-video-pipeline
Use when executing and verifying Jetson Video Codec SDK or PyNvVideoCodec encode/decode, transcode, segmentation, container decode, AV1, or acceptance workflows with exact artifact handoffs.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
holohub-app-lifecycle
Use for non-failing HoloHub app work with ./holohub: scaffold, build, run, test, visual evidence, lint, and flow benchmarking.
tia-testsuite
TIA Portal V21 Test Suite operations. Use for Application Tests with PLCSIM, Style Guide rules, System Tests through OPC UA, import/scope management, execution, and recursive result evaluation.
simulation
Use when materializing and running a module's UVM TB from an approved verification plan (regression, coverage); not for plan authoring or RTL changes.
archetype-lint
This skill should be used when the user asks to "lint an archetype", "validate an archetype", "check archetype compliance", "check archetype rules compliance", or "run archetype rules". Applies 24 normative lint rules with ERROR/WARNING/INFO severity. Supports STRICT and PERMISSIVE modes. Reports violations only — it…