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 triage-my-numbergit 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/triage-my-number)<a href="https://agentmods.dev/skills/debabsah/analytics-office/triage-my-number"><img src="https://agentmods.dev/badge/skills/debabsah/analytics-office/triage-my-number/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/debabsah/analytics-office/triage-my-number"><img src="https://agentmods.dev/badge/skills/debabsah/analytics-office/triage-my-number.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.00215 | $0.03152 |
| Opus 5 | $0.00108 | $0.01576 |
| Sonnet 5 | $0.00043 | $0.00630 |
| Haiku 4.5 | $0.00021 | $0.00315 |
Grade A, and why
triage-my-number 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 10d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
triage-my-number
The colleague you grab when a number comes out wrong: helps you find out why it moved before you tell anyone what it means — systematically, without tunnelling on the first guess or reaching for the data yourself.
When to use
Fire when a number, metric, or result is wrong, suspicious, or moved unexpectedly and the question is "why" — before it gets explained to anyone. Triggers: "why is this number wrong", "churn/revenue/signups jumped — why", "these two numbers don't match", "the dashboard looks off", "this doesn't reconcile", "did something break overnight".
Do NOT fire to review a specific query you already suspect (that's review-my-query), to pin what the metric should mean (kpi-contract), to orient on an unfamiliar estate (groundwork), or to rehearse defending a finished number (defend-my-number). This diagnoses why a result is wrong across the whole path; the code is only one branch of the differential.
This vs. its neighbors: the gate is a symptom in hand. Fire when a number is already wrong/moved and you run the whole 5-branch differential to find the cause. No symptom yet — about to build on or present a number whose premises are unexamined → audit-my-assumptions (preventive, upstream). A specific query to check → review-my-query.
The trap this exists to beat
Asked "why is this number wrong," a capable analyst does the analytical part well — reads the code, names plausible causes. Then, under the pressure that always comes with a broken number ("the board call is in 90 minutes"), it does two wrong things. It tunnels: it latches onto the most-likely cause and writes it into the story for leadership before a single check ties it to this number. And it lunges at the data: handed a sample "to see the shape," it computes — runs the logic over the rows "just to confirm the mechanism" — crossing the read-only line. The result is a confident cause that is really a suspect, handed to a stakeholder as a verdict. This skill holds the differential: it enumerates the whole failure surface, attaches a discriminating check to each candidate, keeps "a defect you can read" separate from "the cause of this number," directs you to run the checks, and gives the stakeholder a calibrated holding line — not a guess.
What ships with it
3 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.
- 10d ago First seen · 72 lines · 0 tokens per session scan A 41a76fa07825
triage-my-number is a skill published in the GitHub repository debabsah/analytics-office (9 stars, last pushed 3mo ago), licensed MIT. It adds 215 tokens to every session and 3,152 once invoked, about $0.0011 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
release-it
Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "deployment pipeline", "chaos engineering", "retry storm", "health checks", "my service keeps crashing", "prevent cascading failures", or…
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
debug
Interactive debugging workflow with hypothesis-driven probe loop. Use when: unknown bugs, script errors, silent failures, troubleshooting. Not for: known bugs (use bug-fix), GitHub issue analysis (use issue-analyze), code understanding (use code-explore). Output: debug report with probe journal + root cause + fix.
git-investigate
Git history investigation. Use when: tracking code changes, finding where bugs were introduced, root cause analysis. Not for: code exploration (use code-explore), issue analysis (use issue-analyze). Output: history trace + root cause report.
analyze
Deep-dive codebase analysis that explains how things actually work — business rules, architecture patterns, auth flows, data models, integrations, and performance hotspots. Use whenever the user asks "how does X work", "map the Y flow", "what are the business rules for Z", "trace the auth path", "explore the codebase…
simplify
Wrap-up refactoring — simplify code, eliminate duplication, preserve behavior.