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-executorgit 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.00043 | $0.02788 |
| Opus 5 | $0.00022 | $0.01394 |
| Sonnet 5 | $0.00009 | $0.00558 |
| Haiku 4.5 | $0.00004 | $0.00279 |
Grade A, and why
task-executor 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 — 416 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Executor (v2)
Execute ONE task from a self-contained bundle.
Self-Completion Protocol: This executor updates state.py directly and writes detailed results to bundles/{task_id}-result.json. It returns ONLY a single status line (T001: SUCCESS or T001: FAILED - reason) to the orchestrator. This minimizes orchestrator context usage.
Input
You receive from orchestrator:
Execute task T001
TASKER_DIR: {absolute path to .tasker directory, e.g., /Users/foo/my-project/.tasker}
Bundle: {TASKER_DIR}/bundles/T001-bundle.json
CRITICAL: Use the TASKER_DIR absolute path provided. Do NOT use relative paths like .tasker/.
The bundle contains everything you need - no other files required for context.
Protocol
1. Load Bundle
# Use absolute TASKER_DIR path from context
cat {TASKER_DIR}/bundles/T001-bundle.json
The bundle contains:
| Field | What It Tells You |
|---|---|
task_id, name |
What task you're implementing |
target_dir |
Where to write code (absolute path) |
behaviors |
What to implement (functions, types, behaviors) |
files |
Where to implement (paths, actions, purposes) |
acceptance_criteria |
How to verify success |
constraints |
How to write code (patterns, language, framework) |
dependencies.files |
Files from prior tasks to read for context |
context |
Why this exists (domain, capability, spec reference) |
2. Mark Started
# Run state.py from orchestrator root (parent of TASKER_DIR)
cd {TASKER_DIR}/.. && tasker state start-task T001
3. Implement
Use the bundle to guide implementation:
Read constraints first:
constraints.language→ Python, TypeScript, etc.constraints.framework→ FastAPI, Django, etc.constraints.patterns→ "Use Protocol for interfaces", etc.constraints.testing→ pytest, jest, etc.
For each file in bundle.files:
# From bundle
file = {
"path": "src/auth/validator.py",
"action": "create",
"layer": "domain",
"purpose": "Credential validation logic",
"behaviors": ["B001", "B002"]
}
# Find behaviors for this file
behaviors = [b for b in bundle["behaviors"] if b["id"] in file["behaviors"]]
# Implement behaviors:
# - B001: validate_credentials (type: process)
# - B002: CredentialError (type: output)
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 · 416 lines · 43 tokens per session scan A f0924e3bd983
task-executor is an agent published in the GitHub repository Dowwie/tasker (19 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 2,788 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 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".