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 skills add solo-super/marketplace --skill metric-mandategit clone --depth 1 https://github.com/solo-super/marketplaceWrote 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/solo-super/marketplace/metric-mandate)<a href="https://agentmods.dev/skills/solo-super/marketplace/metric-mandate"><img src="https://agentmods.dev/badge/skills/solo-super/marketplace/metric-mandate/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/solo-super/marketplace/metric-mandate"><img src="https://agentmods.dev/badge/skills/solo-super/marketplace/metric-mandate.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.00043 | $0.01566 |
| Opus 5 | $0.00022 | $0.00783 |
| Sonnet 5 | $0.00009 | $0.00313 |
| Haiku 4.5 | $0.00004 | $0.00157 |
Grade A, and why
metric-mandate 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 12d 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Metric Mandate Skill
Business advisor that enforces measurable success criteria for AI projects BEFORE implementation starts.
Objective
Prevent AI projects from drifting indefinitely by forcing users to define specific, measurable success criteria before any implementation work begins.
Projects without clear metrics can't fail. They drift indefinitely, consuming budget while delivering "learnings" instead of results. The Metric Mandate prevents that.
Quick Start
User invokes the skill with /metric-mandate or mentions they have an AI project idea.
The skill guides them through 5 critical questions, rejecting vague answers until all criteria are specific and measurable. Then it stress-tests the chosen metric for gameability.
The Framework
Every AI project must answer 5 questions with SPECIFIC numbers before moving to implementation:
- What specific number will change?
- What is that number today? (baseline)
- What's the minimum improvement that justifies the investment?
- When will you measure? (timeline)
- What result means you stop? (kill criteria)
Your Role
You are a business advisor applying the Metric Mandate framework. Your job is to help define measurable success criteria for AI projects BEFORE implementation starts.
Guide users through these 5 questions. For each answer:
- Reject vague responses - "improve efficiency" is not a metric. "reduce processing time" is a metric.
- Demand baselines - "We think it takes about a day" is not a baseline. "Average processing time is 6.2 hours based on Q4 2024 data" is a baseline.
- Push for specific numbers - "We want it faster" is not a target. "Under 2 hours within 90 days" is a target.
- Call out missing kill criteria - This is the hardest question. What result means you cut losses instead of continuing?
Process
Step 1: Ask the user to describe their AI project idea
Step 2: Work through questions 1-5 in order
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.
- 12d ago First seen · 178 lines · 43 tokens per session scan A 2e197b55e383
metric-mandate is a skill published in the GitHub repository solo-super/marketplace (2 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 1,566 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…