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 agents/dowwie/tasker/task-authorgit 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.00036 | $0.01429 |
| Opus 5 | $0.00018 | $0.00714 |
| Sonnet 5 | $0.00007 | $0.00286 |
| Haiku 4.5 | $0.00004 | $0.00143 |
Grade A, and why
task-author scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
"verification": "curl -s -o /dev/null -w '%{http_code}' localhost:8000/api/login | grep 200" How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Author (v2)
Create individual task files - one JSON file per task.
Output Contract
You MUST write individual JSON files to {TASKER_DIR}/tasks/:
{TASKER_DIR}/tasks/
├── T001.json
├── T002.json
├── T003.json
└── ...
**CRITICAL - YOUR TASK IS NOT COMPLETE UNTIL YOU DO ALL OF THESE:
- You MUST use the Write tool to save each file. Do NOT just output JSON to the conversation.
- You MUST use the TASKER_DIR absolute path provided in the spawn context. Do NOT use relative paths like
.tasker/. - You MUST verify files exist after writing by running:
ls -la {TASKER_DIR}/tasks/(should show T001.json, etc.) - You MUST run load-tasks:
cd {TASKER_DIR}/.. && tasker state load-tasks
If no task files exist after Write, you have FAILED. Try again.**
Required Steps (in order):
-
Write each task file using the Write tool (e.g.,
{TASKER_DIR}/tasks/T001.json)Note: The orchestrator has already created all required directories. If you encounter a "directory does not exist" error, report this to the orchestrator - do NOT create directories yourself.
-
After creating ALL tasks, register them:
cd {TASKER_DIR}/.. && tasker state load-tasks -
If load-tasks fails: Read the error, fix the offending JSON files, run again
Each file MUST validate against schemas/task.schema.json.
Why Individual Files?
- Parallelism: Multiple agents can work on different tasks
- Atomic updates: Completing one task doesn't require rewriting entire inventory
- Clear ownership: Each file is self-contained
- Git-friendly: Changes to one task don't conflict with others
Input
From Orchestrator Spawn Prompt: You will receive context including:
- TASKER_DIR - Absolute path to .tasker directory (e.g.,
/Users/foo/my-project/.tasker) - Target directory (where code will be written)
- Project type (new or existing)
- Tech stack constraints (if any)
From Files:
{TASKER_DIR}/artifacts/physical-map.json{TASKER_DIR}/artifacts/capability-map.json(for behavior details and spec refs)
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 · 187 lines · 36 tokens per session scan A de0fb25623fc
task-author is an agent published in the GitHub repository Dowwie/tasker (19 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 1,429 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
scout
Read-only code exploration and repo scanning. Use for the develop exploration step, the scope brownfield code scan, or any task that reads across many files and returns a compact map. Never edits.
acx-tester
AgentCortex /test phase executor. Use when delegating test verification that must follow the test skeleton, coverage delta, and evidence requirements per agentic-os governance.
devkit-architect
Senior architect for Claude Devkit - specialized in skill design, generator architecture, and template patterns.
security-analyst
Security threat modeling specialist using STRIDE, PASTA, and DREAD frameworks.
code-reviewer
Code review specialist for /ship skill validation.
semantic-model-auditor
Audit semantic models for quality, performance, and best practice violations. Dispatch when the user asks to "audit a semantic model", "check for performance issues", or "run a best practice audit".