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/dowwie/tasker/specifynpx skills add Dowwie/tasker --skill specifygit clone --depth 1 https://github.com/Dowwie/taskerWhat 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.00032 | $0.18418 |
| Opus 5 | $0.00016 | $0.09209 |
| Sonnet 5 | $0.00006 | $0.03684 |
| Haiku 4.5 | $0.00003 | $0.01842 |
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.
How it starts
The opening of the file, as written. The whole thing — 2,408 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Specify Workflow
IMPORTANT: All tasker working files go in $TARGET_DIR/.tasker/. Do NOT create any other directories like project-planning/, planning/, or schemas/ at the target project root. The .tasker/ directory is the ONLY location for tasker artifacts (including .tasker/schemas/ for JSON schemas).
An agent-driven interactive workflow that transforms ideas into actionable specifications with extracted capabilities, ready for /plan to decompose into tasks.
Core Principles
- Workflows and invariants before architecture - Never discuss implementation until behavior is clear
- Decision-dense, not prose-dense - Bullet points over paragraphs
- No guessing — Uncertainty becomes Open Questions
- Minimal facilitation — Decide only when required
- Specs are living; ADRs are historical
- Less is more — Avoid ceremony
Artifacts
Required Outputs (in TARGET project)
- README —
{TARGET}/README.md(project overview - what it is, how to use it) - Spec Packet —
{TARGET}/docs/specs/<slug>.md(human-readable) - Capability Map —
{TARGET}/docs/specs/<slug>.capabilities.json(machine-readable, for/plan) - Behavior Model (FSM) —
{TARGET}/docs/state-machines/<slug>/(state machine artifacts, for/planand/execute) - ADR files —
{TARGET}/docs/adrs/ADR-####-<slug>.md(0..N)
Working Files (in target project's .tasker/)
- Session state —
$TARGET_DIR/.tasker/state.json(persistent, primary resume source) - Spec draft —
$TARGET_DIR/.tasker/spec-draft.md(working draft, written incrementally) - Discovery file —
$TARGET_DIR/.tasker/clarify-session.md(append-only log) - Stock-takes —
$TARGET_DIR/.tasker/stock-takes.md(append-only log of vision evolution) - Decision registry —
$TARGET_DIR/.tasker/decisions.json(index of decisions/ADRs) - Spec Review —
$TARGET_DIR/.tasker/spec-review.json(weakness analysis)
Archive
After completion, artifacts can be archived using tasker archive for post-hoc analysis.
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 · 2,408 lines · 32 tokens per session scan A f7d935f38297
specify is a skill published in the GitHub repository Dowwie/tasker (19 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 32 tokens to every session and 18,418 once invoked, about $0.0002 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
debug
Run /debug to find and fix a bug's root cause: a test failing for an unclear reason, /check verify finding a failure, or behavior being wrong. Runs a reproduce, localize, hypothesize, test, fix, verify loop, makes the minimal fix, and hands a regression test to /test. No features, no extra refactors.
red-team-adversarial
Adversarial security and resilience analysis — auto-triggered during /review and /test based on task classification. Provides attack surface analysis, boundary testing, auth bypass attempts, dependency chain attacks, and Beast Mode stress testing.
auth-security
Secure authentication and authorization when credentials, sessions, roles, or permissions change.
karpathy-principles
Behavioral guidelines to reduce common LLM coding mistakes — Think Before Coding, Simplicity First, Surgical Changes, Goal-Driven Execution.
database-design
Design schemas and migrations when persistent data structures change.
verification-before-completion
Enforce "no evidence = no completion"; run Gate Function verification before declaring done.