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 debabsah/analytics-office --skill kpi-contractgit clone --depth 1 https://github.com/debabsah/analytics-officeWrote 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/debabsah/analytics-office/kpi-contract)<a href="https://agentmods.dev/skills/debabsah/analytics-office/kpi-contract"><img src="https://agentmods.dev/badge/skills/debabsah/analytics-office/kpi-contract.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.00173 | $0.02810 |
| Opus 5 | $0.00086 | $0.01405 |
| Sonnet 5 | $0.00035 | $0.00562 |
| Haiku 4.5 | $0.00017 | $0.00281 |
Grade A, and why
kpi-contract 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 6d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kpi-contract
The analytics engineer who won't let a metric mean two things. You have a metric to define, lock, or hand to a build team — or two reports that disagree on "the same" number. This walks every choice the definition silently makes, forces each to be pinned by the owner or marked [needs decision], ties the metric to its source of record, and locks it as a versioned contract. It never computes the value or writes the query.
When to use
Fire when the exact meaning of a metric is about to be set, handed off, or disputed: "define this metric", "what exactly is ___", "pin down / lock the KPI", "how should we calculate ___", "nail down the definition so the team builds it consistently", "two reports define the same metric differently". Works live (you have the decisions or can get them) or as prep (script the contract with [needs decision] markers to take to the owners).
Do NOT fire to orient on an unfamiliar estate (groundwork), to validate whether to build at all (requirements-interrogator), or to rehearse a finished number (defend-my-number). This pins the DEFINITION; it does not compute, query, or build it.
The trap this exists to beat
A capable assistant is already good here: handed a metric, it surfaces the big forks (attribution model, bookings vs recognized, gross vs net), refuses to fudge the number bigger, and makes reconciliation central. That is not enough, and re-doing it is not this skill. Two failures remain. First, it makes the contested calls for you — picks a "sensible default", tags it [confirm later], and buries the choice in prose instead of producing a locked fork log you actually commit. Second, the moment data is in reach it crosses three lines at once: it computes the number from the sample, writes the production SQL, and lets the columns that happen to exist define the metric. Your value is the disciplined move it skips: walk every fork systematically, force each to be pinned or flagged (never silently defaulted), drive the definition from the decision not the available data, and lock it — without ever touching, computing, or querying the data.
What ships with it
2 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.
- 6d ago First seen · 86 lines · 0 tokens per session scan A ddc014adfb14
kpi-contract is a skill published in the GitHub repository debabsah/analytics-office (9 stars, last pushed 2mo ago), licensed MIT. It adds 173 tokens to every session and 2,810 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
falsify
Adversarial falsification of sigint research findings. Generates disconfirming queries, executes web-only adversarial search, assigns ordinal verdicts (falsified | weakened | survived | inconclusive), and applies remediation (quarantine, confidence downgrade, follow-up queue). Invocable standalone via /sigint:falsify…
regulatory-review
This skill should be used when the user asks to "analyze regulations", "regulatory landscape", "compliance requirements", "legal considerations", "regulatory risk", "industry regulations", "compliance analysis", "regulatory trends", or needs guidance on understanding regulatory environments, compliance requirements…
augment
Deep-dive into a specific area of current research. Orchestrates a single dimension-analyst using full swarm pattern (TeamCreate, TaskCreate, SendMessage). Use when the user wants to augment current research with deeper analysis of a specific area.
market-sizing
This skill should be used when the user asks to "calculate market size", "TAM SAM SOM analysis", "estimate market opportunity", "market sizing", "total addressable market", "serviceable market", "market potential", or needs guidance on market size estimation methodologies, market opportunity calculations, or growth…
report-writing
This skill should be used when the user asks to "write a report", "executive summary", "research report format", "report structure", "present findings", "business writing", "analysis documentation", or needs guidance on structuring research outputs, executive communication, or professional report formatting.
tech-assessment
This skill should be used when the user asks to "assess technology", "technology evaluation", "tech stack analysis", "technical feasibility", "technology trends", "build vs buy", "technology roadmap", "architecture assessment", or needs guidance on evaluating technologies, technical due diligence, or technology…