An interactive workflow for writing a software specification: the document that explains a feature's goal, behavior, and boundaries.

Use it to define a feature's vision, clarify what it should support, and describe the behaviors that need to be built.

It helps turn an early idea into clarified requirements before implementation begins.

specify — Command by Dowwie

Install

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.

agentmods

npx agentmods add commands/dowwie/tasker/specify

Clone the repo

git clone --depth 1 https://github.com/Dowwie/tasker

Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 32 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00012	$0.00032
Opus 5	$0.00006	$0.00016
Sonnet 5	$0.00002	$0.00006
Haiku 4.5	$0.00001	$0.00003

Measured 2d ago against content hash 0ee76d13f4bc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

specify 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 2d 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.

commands/specify.md · 6 lines

What it actually says

Use the tasker:specify skill to run the interactive specification workflow.

Changes

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.

2d ago First seen · 6 lines · 12 tokens per session scan A 0ee76d13f4bc

Subscribe to this mod's changes

specify is a command published in the GitHub repository Dowwie/tasker (19 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 32 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.

Documents Productivity Writing and docs agentic-development claude-code

specify

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

spec-intake

ask-local

brainstorm

govern-audit

retro

review