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/eilodon/calm/calm-guidenpx skills add Eilodon/CALM --skill calm-guidegit 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/calm-guide)<a href="https://agentmods.dev/skills/eilodon/calm/calm-guide"><img src="https://agentmods.dev/badge/skills/eilodon/calm/calm-guide.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.00126 | $0.00805 |
| Opus 5 | $0.00063 | $0.00402 |
| Sonnet 5 | $0.00025 | $0.00161 |
| Haiku 4.5 | $0.00013 | $0.00081 |
Grade A, and why
calm-guide 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 4d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CALM MCP workflow — quick trigger
Read AGENTS.md at the project root in full now. It is the single
source of truth for this workflow — this skill exists to make sure you
actually reach for it at the right moment, not to hold a second copy of its
content that would silently drift out of sync with it over time. If
AGENTS.md doesn't exist at the project root, this isn't a CALM-instrumented
repo (or you're in the wrong directory) — stop here, this skill doesn't
apply.
If you only have room for the short version right now
- Orient —
repo_overview()always first, thenhotspots()/fitness_report()as needed. - Locate —
locate(query)(search + file_overview + symbol_info in one call) orsearch(query, kind=...). - Inspect —
source(symbol)for a symbol-precise read, orunderstand(symbol)for locate+source+callers together. - Trace —
callers(symbol),callees(symbol),path(from, to),dependencies(path). - Pre-Edit —
edit_context(symbol): mandatory before touching any real code symbol, no exceptions. (A Markdown/text heading is the one exception — it never carries a blast radius to check.) - Edit —
edit_symbol(...)/edit_lines(...): CALM's own write path, hash-verified, risk-gated, reindexes immediately. Fall back to nativeEdit/Writeonly for a brand-new file or a path CALM doesn't index (dotdirs,target/,node_modules/,dist/,build/, etc.). - Verify —
diff_impact(staged=true): mandatory before any commit or push, no exceptions. - Recover —
session_context()after 10+ calls without progress;remember(topic, content)/recall(topic)for durable cross-session notes.
Steps 5 and 7 are the only hard-enforced ones under Claude Code (a hook
denies the native equivalent without them) — the rest is strongly
recommended, not blocking. Every signal, edge case, and the preset/toolset
reference lives in AGENTS.md — go read it in full if you haven't this
session.
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.
- 4d ago First seen · 61 lines · 126 tokens per session scan A 361d0267f724
calm-guide is a skill published in the GitHub repository Eilodon/CALM (16 stars, last pushed today), licensed MIT. It adds 126 tokens to every session and 805 once invoked, about $0.0006 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
verify-pr
This skill should be used to run a sandboxed deep verification of a qwen-code PR — "/verify-pr ", "深度验证这个 PR", A/B load-bearing proof against the base build, mock-free harnesses with wire oracles, and targeted gates — producing tmp/pr -verify- /report.md plus a machine-readable verdict. Designed for the token-free CI…
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…
desktop-brand-builder
Generate a branded Qwen Code desktop package from the Tauri desktop shell using a minimal brandId and logo. Use when the user wants a custom, white-label, or rebranded desktop client, installer, DMG/EXE/AppImage/deb, or one-click brand build on top of packages/desktop-shell.
agent-reproduce-feature
Use when reproducing an existing Codex or Claude Code feature in Qwen Code or another agent CLI by choosing a reference agent, capturing HTTP request bodies, prompts, tool/function schemas, terminal output, and then implementing the matching behavior in the target repo.