Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/mthines/agent-skillsnpx agentmods add skills/mthines/agent-skills/measurableWrote 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/mthines/agent-skills/measurable)<a href="https://agentmods.dev/skills/mthines/agent-skills/measurable"><img src="https://agentmods.dev/badge/skills/mthines/agent-skills/measurable.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 188 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 185 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 189 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00172 | $0.02927 |
| Opus 5 | $0.00086 | $0.01463 |
| Sonnet 5 | $0.00034 | $0.00585 |
| Haiku 4.5 | $0.00017 | $0.00293 |
Grade A, and why
measurable 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 3d 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Measurable
Makes "we shipped it" and "we can see it" the same statement. A change is only done when its impact is measurable and its regressions are visible — this skill decides what telemetry a diff needs, writes or audits it, and records a per-repo profile so the answer doesn't have to be re-derived every time.
This
SKILL.mdis a thin index. Detailed rules live inrules/*.mdand load on demand. The profile template lives intemplates/*.md.Composes, does not duplicate. Frontend event design is
rum-tracking's job — this skill only decides whether a user-facing change needs RUM and hands off to it. Backend span/metric semantic conventions belong to theotel-instrumentationandotel-semantic-conventionsskills (from the dash0 agent-skills repo) when installed — invoked viaSkill(), skipped silently otherwise, withrules/backend-instrumentation.mdas the built-in fallback. Persistence for the Observability Profile ispersistent-memory'sproject-sharedtier — this skill never invents its own storage layer.
Mode Detection
Parse $1 as the mode.
State the detected mode in one line before continuing.
| Mode | Default | Trigger |
|---|---|---|
guide |
yes | "is this measurable", "what telemetry do I need", default if no mode |
implement |
"add telemetry", "instrument this", "add RUM and API telemetry" | |
audit |
"audit observability", "check observability coverage", "--diff", aw Phase 4 gate | |
setup |
"set up observability profile", "first-time setup", "/measurable setup" |
If $1 is a diff, PR, file, or directory, treat it as the scope for
implement or audit.
What ships with it
7 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.
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.
- 3d ago Changed · +2 lines 052210461ecb
- 4d ago Changed · +8 lines de2bcac1d01a
- 8d ago First seen · 223 lines · 172 tokens per session scan A 5f81b45a22fe
measurable is a skill published in the GitHub repository mthines/agent-skills (13 stars, last pushed today), licensed MIT. It adds 172 tokens to every session and 2,927 once invoked, about $0.0009 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
debugging-and-error-recovery
Enforces a stop-the-line triage protocol across failure classes — test failures, build breaks, runtime errors, and production incidents — using bisection, safe-fallback design, and instrumentation lifecycle management. Use when any unexpected failure appears and the question is "what class of failure is this and…
go-expert
Use when writing or reviewing Go code that starts goroutines, holds a sync.Mutex/RWMutex, or closes channels - to enforce goroutine lifecycle ownership, lock-hygiene, and channel-close-side rules, and to wire up the detection tooling (go test -race, go vet, go.uber.org/goleak) that catches violations tests alone…
security-analysis
Runs a two-pass vulnerability scan on a snippet, file, or diff — a static pattern pass across fixed categories (injection, secrets, auth, crypto, deserialization, path traversal, resource exhaustion), then an LLM-reasoning pass for business-logic and race-condition flaws the patterns can't catch. Use for a dedicated…
debug
Runs a tight four-phase loop — reproduce, isolate, diagnose, fix — to root-cause a single bug with evidence, not guesses. Use when given a specific error message, stack trace, or unexpected behavior for one bug and need a fast, mechanical session (reproduce → isolate → diagnose → fix → prevention). For broader…
layered-logging-and-alerting-patterns
Guides services where a single logging call fans out to multiple side effects - error tracking (e.g. Sentry), a centralized log-shipping endpoint, and chat/webhook alerting - rather than just writing a log line. Use when adding a log statement to a service with this shape, reviewing why removing a "log statement"…
bug-triage-and-severity-classification
This skill should be used when the user asks to "triage this bug", "what severity is this", "classify this incident/bug", "is this a Sev1 or Sev2", "what priority should this ticket be", or is deciding SLA/response urgency for a reported defect. Use for assigning severity and priority to bugs and incidents…