Borrowing it
Nothing to install: this file belongs to Eilodon/CALM. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Eilodon/CALM/main/.claude/skills/vheatm/SKILL.mdgit clone --depth 1 https://github.com/Eilodon/CALMWrote 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/eilodon/calm/vheatm)<a href="https://agentmods.dev/skills/eilodon/calm/vheatm"><img src="https://agentmods.dev/badge/skills/eilodon/calm/vheatm/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/eilodon/calm/vheatm"><img src="https://agentmods.dev/badge/skills/eilodon/calm/vheatm.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.00149 | $0.14087 |
| Opus 5.5 | $0.00060 | $0.05635 |
| Sonnet 5.5 | $0.00030 | $0.02817 |
| Haiku 4.5 | $0.00015 | $0.01409 |
Grade A, and why
vheatm 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 1mo 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 — 879 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VHEATM 16.0 — ULTIMATE
"Every claim has an anchor. Every fix has an anchor. Every pattern is global. Every cycle assumes more bugs remain. Every bug has an owner. Every ownership boundary is a risk multiplier. Every temporal state is a slow-motion bug waiting for its trigger. Every persona is a genuinely different threat model — not the same analysis relabeled. Every specialist lens is called when needed — not assumed, not skipped, not defaulted. Every section must produce output — not ceremony. The audit itself must be defended against adversarial inputs. The framework must audit itself. The framework must measure its own accuracy — not just its process. The framework must survive challenge by alternatives. The auditor must not judge its own work — an independent judge must. Every audit knows what it is." ─── final pillar recovered from VHEATM 8.0
Three Trust Anchors (recovered from v8 and v10)
These three rules survive every cycle, every mode, every tier. They were lost between v12 and v14 and are explicitly restored in v16:
-
"Read-only by default. VHEATM recommends, never self-executes." (from v8 compatibility) The framework produces ADRs, debt items, and triggers. It does not apply patches, run commands, or modify the codebase. Every action carries a human-in-the-loop gate.
-
"Every audit knows what it is." (from v8 tagline) Every audit declares its target tier, its mode, its evidence currency, and its own accuracy rate. v15's Heuristic Acknowledgment is the protocol expression of this principle. No anonymous authority claims.
-
"LIVE vs ENTERPRISE = fix-path ownership, not regulatory scope alone." (from v10) A single-team system under GDPR → LIVE + L7.11. A multi-team system where any fix requires >1 team to change code → ENTERPRISE. The discriminator is who has to act, not what regulation applies. Lost from v12 SKILL.md — restored here.
VHEATM's Position (re-stated v16)
What ships with it
33 files 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.
- references/00-context-modes.md 7.8 KB
- references/01-phase-guide.md 53 KB
- references/02-bias-probes.md 6.5 KB
- references/03-ux-lens.md 3.0 KB
- references/04-automation-bias-guard.md 4.5 KB
- references/05-signal-noise-filter.md 3.0 KB
- references/06-output-schemas.md 11 KB
- references/07-stakeholder-templates.md 6.4 KB
- references/08-pattern-globalization.md 8.1 KB
- references/09-fix-verification.md 6.2 KB
- references/10-adversarial-pass.md 10 KB
- references/11-cross-cutting-layer.md 15 KB
- references/12-compound-feature-decomp.md 13 KB
- references/13-bug-class-catalog.md 22 KB
- references/14-incentive-misalignment.md 8.7 KB
- references/15-org-blast-radius.md 11 KB
- references/16-temporal-scan-mode.md 12 KB
- references/17-hybrid-verification.md 10 KB
- references/18-ai-native-addenda.md 16 KB
- references/19-language-profiles.md 14 KB
- references/20-architecture-smells.md 9.6 KB
- references/21-runtime-controller.md 12 KB
- references/22-specialist-lens-router.md 16 KB
- references/23-atam-utility-tree.md 8.6 KB
- references/24-fmea-lite.md 9.9 KB
- references/25-assurance-maturity-overlay.md 9.9 KB
- references/26-nist-ai-rmf-overlay.md 9.2 KB
- references/27-l4-sublayers.md 11 KB
- references/28-auditor-defense.md 15 KB
- references/29-execution-fidelity.md 9.8 KB
- references/30-framework-lifecycle.md 32 KB
- references/31-code-path-trace.md 13 KB
- SYNTHESIS_REPORT.md 18 KB
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.
- 1mo ago First seen · 879 lines · 149 tokens per session scan A 64674368471f
vheatm is a skill published in the GitHub repository Eilodon/CALM (17 stars, last pushed 6d ago), licensed MIT. It adds 149 tokens to every session and 14,087 once invoked, about $0.0006 per session on Opus 5.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
autofix-pr
Watch a pull request and fix it from a worktree of its own - CI failures, review feedback from trusted authors and merge conflicts are fixed, pushed to the PR branch and answered on the PR under the user's git and gh identity. Usage - /autofix-pr [ | ] [--once] [--every ] [--no-reply] [--yes] [instructions]…
simplify
Review recent code changes for reuse, code quality, and efficiency, then directly apply straightforward cleanup improvements. Use when the user wants a post-implementation cleanup pass, pre-PR polish, or asks to simplify/refine recent changes. Invoke with /simplify or /simplify .
triage
Gatekeep and review GitHub issues and pull requests for Qwen Code maintainers. Use for GitHub Action issue triage, PR admission checks, product-direction review, KISS-focused PR review, and staged bilingual GitHub comments.
autofix
Review and repair current local changes until they converge, or run Qwen Code Autofix issue and review workflows from GitHub Actions.
find-simplifications
Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…
enola
Use Enola when investigating architecture, dependencies, blast radius, cross-repository relationships, structural regressions, or what a code change did to the system.