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 agentmods add skills/saadshahd/moo.md/interrogatenpx skills add saadshahd/moo.md --skill interrogategit clone --depth 1 https://github.com/saadshahd/moo.mdWrote 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/saadshahd/moo.md/interrogate)<a href="https://agentmods.dev/skills/saadshahd/moo.md/interrogate"><img src="https://agentmods.dev/badge/skills/saadshahd/moo.md/interrogate.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 | $0.00026 | $0.00685 |
| Opus 5 | $0.00013 | $0.00342 |
| Sonnet 5 | $0.00005 | $0.00137 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
interrogate 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 5d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Extract
From the conversation/context/user:
- The proposal as committed — locked, chosen, or declared.
- Its decisions — the choices inside it the user has not defended.
Gate
Proceed only when: the proposal is committed, its decisions need the user to defend them, and a decision falling under questioning would change what gets built.
Anything else, say which in one plain line — never interrogate anyway:
- The user hasn't committed, and holds what they cannot yet say → use elicit skill — there is nothing to defend, something to draw out.
- The user hasn't committed and is still weighing — nothing locked, chosen, or declared → there is nothing to defend yet.
- The user wants a verdict — the proposal exists and they're asking whether it is right, not standing behind it → use judge skill.
- Every question the proposal raises is answerable from the repo or the record — nothing needs the user → this is a review, not a questioning: run it yourself, answer each question from what is there, and proceed with what the review finds.
- No decision inside it would change what gets built, whatever the answers → skip the questioning and proceed with the work.
Steelman
State the strongest case for the proposal as committed — the best reasons it is right — before any attack. Then assume it is wrong somewhere and go find where.
Press
- Attack one decision at a time: what breaks if this is wrong, what it traded away, why this over the nearest alternative.
- Only ask what the user alone can answer. Anything answerable from the repo or the record, answer yourself and move on.
- Do not accept a vague answer — "fast" gets "fast how, what number?".
- Sort each answer before moving on:
- it stands → keep it as the decision's defence
- it changes the proposal → record it as an amendment
- it exposes another decision the user has not defended → add that decision and press it next.
- Continue until every surfaced decision carries a defence or an amendment in the user's own words. Stopping earlier is allowed only by naming the decisions left undefended.
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.
- 5d ago First seen · 53 lines · 26 tokens per session scan A 8cf1c5ab5154
interrogate is a skill published in the GitHub repository saadshahd/moo.md (34 stars, last pushed 19d ago), licensed MIT. It adds 26 tokens to every session and 685 once invoked, about $0.0001 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-30.
Other skills, from other repositories
session-recap
Document Claude Code sessions by extracting knowledge into cross-referenced documentation. Triggers on "recap the session", "summarize the work", or after significant code changes.
knowledge-bank-lookup
Delegates knowledge bank lookups to Explore subagents with reflections-first strategy that learns from past mistakes. Checks /reflections/ directory before documentation to extract documented failures to avoid and proven approaches to apply. Automatically triggers when user mentions services ([project-a], [project-b]…
lark-openapi-explorer
飞书/Lark 原生 OpenAPI 探索：从官方文档库中挖掘未经 CLI 封装的原生 OpenAPI 接口。当用户的需求无法被现有 lark- skill 或 lark-cli 已注册命令满足，需要查找并调用原生飞书 OpenAPI 时使用。.
lark-workflow-standup-report
日程待办摘要：编排 calendar +agenda 和 task +get-my-tasks，生成指定日期的日程与未完成任务摘要。适用于了解今天/明天/本周的安排。.
kb-ingest
Ingest external sources into the knowledge bank through interactive study or quick filing. Two modes — Quick (summarize → file) and Study (theme-by-theme deep dive with online research and personal notes → multi-layer KB output → optional blog/slack synthesis). Triggers on "ingest this", "study this article", "add to…
session-manager
Manage current Claude Code session metadata — set project, tags, and summary on session.md via Obsidian CLI. Use this skill whenever the user wants to tag, categorize, name, label, summarize, or organize the current session. Triggers on phrases like "tag this session", "this was about X", "mark this as", "session…