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 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/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/outlinedriven/outline-driven-development/askme"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/askme.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 29 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 51 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 69 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00056 | $0.04388 |
| Opus 5.5 | $0.00022 | $0.01755 |
| Sonnet 5.5 | $0.00011 | $0.00878 |
| Haiku 4.5 | $0.00006 | $0.00439 |
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 22d 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 — 97 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 or elicitation request; long, bundled, high-stakes, hard-to-undo instruction; ambiguous scope or referents; or explicit mode: exhaustive, collaborative, adversarial, gate, batch, interview, scan, or proposal. |
| Authority | Reversible local. Writes only the user-approved decision log file in interview mode or one durable "understood as: ..." log line for substantial work after gate decision; every other mode emits chat output only. Rollback is deleting that file or log line. Before the gate passes, no file, VCS, credential, paid, published, or deployed mutation is permitted. No remote mutation. |
| Side effect | Question sets, findings reports, and intent proposals in chat; interview mode writes one named local file after approval; gate mode writes one durable understood-as log line for substantial work after the gate decision and nothing before it; no other mode writes. |
| Done | The selected mode's terminal state holds: intent confirmed, frontier empty, record approved and written, no open manual finding, proposal answered, or gate mode stopped on no signal or passed after a paraphrased, context-checked restatement with any genuine fork surfaced, the required substantial-work log line written, and no premature action. |
Inputs
- The user's task, request, or handed-over material (required).
- Mode selector:
exhaustive(default),collaborative,adversarial,gate,batch,interview,scan, orproposal. Auto-detected from invoking phrasing; an explicit mode argument always overrides auto-detection. - 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. Gate mode may fire at most one clarifying question. - Mode-specific inputs:
scantakes an optional text-or-path target;proposalrequires the handed-over material;interviewrequires a stated goal;gatetakes the user's instruction plus all readable context (current message, session history, project memory, filesystem, and established conventions), with no separate artifact required.
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.
- 22d ago Changed 4592120f2683
- 1mo ago Changed · +12 lines · +10 tokens per session f8a3f75ec712
- 1mo ago Changed · +21 lines · -23 tokens per session a5f8e30b33e6
- 1mo ago First seen · 64 lines · 69 tokens per session scan A 9168ed42cb6a
askme is a skill published in the GitHub repository OutlineDriven/outline-driven-development (53 stars, last pushed 22d ago), licensed Apache-2.0. It adds 56 tokens to every session and 4,388 once invoked, about $0.0002 per session on Opus 5.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
audit-project
Run an iterative multi-agent code audit until critical and high findings are resolved. Use when the user says "audit my code", "find all the bugs", "deep code audit", "iterative review", or "review until clean".
duet
Use when the user invokes /duet, says "pair with me", or faces aesthetic, architectural, or irreversible decisions.
goal-prompt-drafting
Use when asked to draft copy-ready /goal objectives for long-running agents; returns one normalized one-line objective with measurable end state, grounded proof, easy-out invariants, a stop clause, and a Missing list. Not for source or remote-system changes.
handoff-prompt
Use when the user asks for a handoff, delegation, or clipboard-ready prompt for another agent: a standalone path-free prompt copied to the clipboard, confirmed by title. Not for session-snapshot briefs — use handoff; never remote, credential, publish, deploy, or irreversible.
publish-branch
Use when asked to publish the checked-out branch: commit and push it on whatever branch it is, the default branch included. Not for creating branches, PRs, force pushes, or pushing any other branch; when the request excludes the default branch, use commit-push-current.
drill
Use when a concept needs practising rather than explaining: run a scaffolded exercise from worked example to independent problem, quiz the learner, run spaced recall over what they cleared, or probe for the gaps blocking what they want next. For explanation, use explain-concept; for an end-to-end build, use capstone.