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 defend-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/defend-my-number)<a href="https://agentmods.dev/skills/debabsah/analytics-office/defend-my-number"><img src="https://agentmods.dev/badge/skills/debabsah/analytics-office/defend-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/defend-my-number"><img src="https://agentmods.dev/badge/skills/debabsah/analytics-office/defend-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.00148 | $0.02395 |
| Opus 5 | $0.00074 | $0.01197 |
| Sonnet 5 | $0.00030 | $0.00479 |
| Haiku 4.5 | $0.00015 | $0.00239 |
Grade A, and why
defend-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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
defend-my-number
The sparring partner who makes you earn the number before the room does. You have a number, finding, or recommendation you'll have to defend. This plays the skeptic you're about to face, drills you under escalating pressure, grades each answer honestly, and leaves a Defense Sheet of the attacks, your best answers, and the holes still to fix.
When to use
Fire before a high-stakes presentation of a result: a stakeholder review, exec readout, board deck, steering meeting. Triggers: "defend this number", "pressure-test my analysis / finding", "they'll push back on this", "poke holes in this", "rehearse for the meeting", "what will they attack". You bring the claim and its context; it brings the skeptic.
Do NOT fire to orient on an unfamiliar estate (that's groundwork) or to validate a request before building (requirements-interrogator). If the number is an experiment / A-B / causal result not yet validated, route to audit-my-experiment FIRST; rehearse once it is audited ship-ready. This rehearses the DEFENSE of a result; it does not compute, verify, or fix the analysis.
This vs. its neighbors. defend REHEARSES the defense out loud under escalating challenge — a stateful, multi-turn drill (defense-sheet.md). To COMPOSE the written brief itself (one pass, one artifact) → brief-my-findings. To surface what you're assuming under the number before you present → audit-my-assumptions.
The trap this exists to beat
Asked to "help me get ready," a capable assistant already does the analytical prep well: it lists the hard questions, stress-tests validity, and offers to run the numbers. Two problems. First, a list you read is not a drill you survive — the freeze in the room is a practiced failure, and so is its cure; you have to answer under live, escalating pressure and find out where you crack. Second, its instinct is to dive into the data and recompute the number "to be sure" — a different job entirely. This skill rehearses whether your reasoning HOLDS UP, in character, out loud, graded. It never recrunches the analysis.
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 · 75 lines · 0 tokens per session scan A 130f02c0a677
defend-my-number is a skill published in the GitHub repository debabsah/analytics-office (9 stars, last pushed 3mo ago), licensed MIT. It adds 148 tokens to every session and 2,395 once invoked, about $0.0007 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
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…
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…
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…
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.
issues
Create GitHub issues from research findings as atomic deliverables. Orchestrates the issue-architect agent using the full swarm pattern (TeamCreate → TaskCreate → Agent(teamname) → SendMessage → TeamDelete). Use this skill when the user invokes /sigint:issues.