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/closetheloops/moradin/measurenpx skills add CloseTheLoops/moradin --skill measuregit clone --depth 1 https://github.com/CloseTheLoops/moradinWrote 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/closetheloops/moradin/measure)<a href="https://agentmods.dev/skills/closetheloops/moradin/measure"><img src="https://agentmods.dev/badge/skills/closetheloops/moradin/measure.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.1 | $0.00062 | $0.01210 |
| Opus 5 | $0.00031 | $0.00605 |
| Sonnet 5 | $0.00012 | $0.00242 |
| Haiku 4.5 | $0.00006 | $0.00121 |
Grade A, and why
moradin-measure 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
moradin:measure
Before researching tools or writing code: what does working look like, in numbers? Without this, you ship blind and every metric you pick later will be one that flatters you. Takes ~10 minutes.
When invoked
/moradin:measure — requires .forge/plan.md (run /moradin:define first if missing). Read plan.md and profile.md. Draft everything from the plan; the operator corrects. Same rule as define: never a blank page.
Build the Success Contract
Work through in order, one at a time:
-
Stage label. From the plan's evidence answer: no evidence the problem exists → stage is validation. Evidence but not shipped → launch. Already has users → growth. Say which and why in one sentence.
-
The one metric that matters. Draft it from the riskiest assumption — the metric should measure exactly the thing v1 must prove. Rules:
- A rate or ratio, never a cumulative total ("% of signups who do X within 7 days", not "total signups"). Totals only go up; they flatter and inform nothing.
- A target ("30%") and a kill/pivot threshold with a sample size ("under 10% after 100 signups"). The threshold is what turns the number into a decision instead of a decoration. Say plainly: "if we hit this line, we change course — agreeing on that now is the whole point."
-
The traffic question. "Where do the first 20 users come from — concretely?" A subreddit they post in, a community they're in, friends in the target group, an audience they have. "Nowhere yet" is a legitimate answer — it means milestone 0 is a validation test (landing page + the concrete channel hunt), because a metric with no visitors is theater.
-
Supporting signals — max 3. Each with a target and a "measured by." Good candidates: a return-rate (do people come back within a week?), the funnel step before the main metric, and the zero-instrumentation fallback below. Refuse a fourth; tracking everything is how measurement gets abandoned.
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 · 53 lines · 62 tokens per session scan A 3dfc3908901a
moradin-measure is a skill published in the GitHub repository CloseTheLoops/moradin (2 stars, last pushed 27d ago), licensed MIT. It adds 62 tokens to every session and 1,210 once invoked, about $0.0003 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
loop-engineering
Use when a repeatable task must become a bounded Trigger -> Execute -> Verify -> State loop, scheduled automation, goal agent, or metric-driven research cycle.
anthropic-os
Use when a personal or team operating system needs a bounded redesign using Four-C, closed-loop controls, 70/30 allocation, 3B creativity, experiments, and prediction-error learning.
knowledge-ops
Use when an Obsidian knowledge system needs classification, deduplication, retrieval, synchronization, debt queues, or governed Agent/Wiki promotion.
verify-before-claim
Use when an agent is about to claim completion, correctness, safety, publication, deployment, or any consequential external fact.
cognitive-compile
Use when source material must be transformed into a compact, evidence-aware model for learning, decisions, or an Obsidian concept note.
creativity-engine
Use when a defined problem needs diverse ideas, cross-domain combinations, and cheap experiments instead of a single untested answer.