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/outlinedriven/outline-driven-development/askmenpx skills add OutlineDriven/outline-driven-development --skill askmegit clone --depth 1 https://github.com/OutlineDriven/outline-driven-developmentWrote 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/outlinedriven/outline-driven-development/askme)<a href="https://agentmods.dev/skills/outlinedriven/outline-driven-development/askme"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/askme.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.00069 | $0.01604 |
| Opus 5 | $0.00034 | $0.00802 |
| Sonnet 5 | $0.00014 | $0.00321 |
| Haiku 4.5 | $0.00007 | $0.00160 |
Grade A, and why
askme 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 yesterday.
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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ask me
Contract
| Field | Bound contract |
|---|---|
| Trigger | Ambiguous task, maximum clarification needed, or explicit exhaustive/collaborative/adversarial askme mode. |
| Authority | Read-only: no file, VCS, credential, paid, published, deployed, or remote mutation. Emits chat output only. |
| Side effect | Verbalized Sampling output and batched question sets written to chat; nothing persisted. |
| Done | Every clarifying question is answered or discharged and intent is confirmed. |
Inputs
- The user's task or request (required).
- Optional mode argument:
exhaustive(default),collaborative, oradversarial. Auto-detected from invoking phrasing; an explicit mode argument always overrides auto-detection. Callers with no mode arg getexhaustive. - An ask-user tool exposing single-select and multi-select questions (the harness equivalent of
AskUserQuestion). Required to fire question batches; if absent, fall back to sequential chat prompts.
Procedure
-
Select mode. Auto-detect from invoking phrasing:
help me refine,walk through with me,let's brainstorm,share tips→ collaborative;poke holes,stress-test,grill,find weaknesses→ adversarial; anything else or no qualifier → exhaustive. An explicit mode argument always wins over auto-detection. -
exhaustive mode — Verbalized Sampling (VS). Sample multiple intent hypotheses; assign each a probability weight on a 0–1 scale; state the falsifier (the specific observation or scenario that would invalidate it) per hypothesis. Expand hypothesis depth as ambiguity, risk, or architectural surface grows; keep it concise when scope is truly narrow. Render the VS block in this format before the first question fire:
1. [Weight: 0.42] hypothesis here
- Falsifier: [observation or scenario that would invalidate this]
2. [Weight: 0.28] hypothesis here
- Falsifier: [observation or scenario that would invalidate this]
- exhaustive mode — exploration. Deliberately seek unconventional, underexplored, and edge-case possibilities relating to the user's objective, drawing on context and plausible but non-obvious requirements. Include at least 3 edge cases (at least 5 if architectural); stop expanding once additional cases no longer change decisions. Broaden sampling if no clear leader emerges. Synthesize surviving hypotheses into one consolidated direction before responding.
What ships with it
1 file 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.
- yesterday First seen · 64 lines · 69 tokens per session scan A 9168ed42cb6a
askme is a skill published in the GitHub repository OutlineDriven/outline-driven-development (52 stars, last pushed yesterday), licensed Apache-2.0. It adds 69 tokens to every session and 1,604 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
outlines
Guarantee valid JSON/XML/code structure during generation, use Pydantic models for type-safe outputs, support local models (Transformers, vLLM), and maximize inference speed with Outlines - dottxt.ai's structured generation library.
brainstorm
Explore vague or ambitious ideas into a right-sized requirements-only plan. Use when the user wants to brainstorm, think through scope, decide what to build, or needs collaborative product framing before planning, not for a decisive verdict on whether to adopt or switch to a specific external technology, library, or…
doc-review
Use when the user asks to review or critique a prose planning document — a plan, spec, PRD, requirements doc, or design doc.
drift-detect
Use when the user says "plan drift", asks whether the roadmap, plans, or docs still match the code, or is deciding what to rebuild when restarting a stalled project. For doc-vs-code drift inside a specific diff, use sync-docs.
setup-gitignore
Use when the user says set up gitignore, fix gitignore, or untracked files keep appearing. Writes or merges .gitignore under stable section anchors and proves reruns produce no diff. Not for remote, credential, publish, deploy, or irreversible changes.
enhance
Audit and tighten agent/plugin surfaces. Use when the user asks to enhance a plugin config, agent definition, skill, or CLAUDE.md.