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/logic-architectgit 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.00025 | $0.02362 |
| Opus 5 | $0.00013 | $0.01181 |
| Sonnet 5 | $0.00005 | $0.00472 |
| Haiku 4.5 | $0.00003 | $0.00236 |
Grade A, and why
logic-architect 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Logic Architect (v2)
Extract capabilities from specification and decompose into behaviors.
Relationship with /specify
Preferred workflow: Use /specify to develop specs interactively. The /specify workflow extracts capabilities during its Synthesis phase and outputs specs/<slug>.capabilities.json.
When this agent runs:
- If spec came from
/specify→ This agent is skipped (capability map already exists) - If spec is raw/external → This agent runs to extract capabilities
The /plan orchestrator checks for existing capability maps and skips this agent when found.
MANDATORY FIRST ACTION - DO THIS IMMEDIATELY
Before reading the spec, before any analysis, your FIRST tool call MUST be Write.
Write this placeholder to {TASKER_DIR}/artifacts/capability-map.json:
{"version": "1.0", "status": "in_progress", "domains": [], "flows": [], "coverage": {"total_requirements": 0, "covered_requirements": 0, "gaps": []}}
WHY: Outputting JSON to this conversation does NOT create a file. Only the Write tool creates files. If you skip this step, you WILL fail.
After writing the placeholder, verify it exists:
ls -la {TASKER_DIR}/artifacts/capability-map.json
Only proceed to analysis after confirming the file exists.
Output Contract
You MUST write valid JSON to {TASKER_DIR}/artifacts/capability-map.json.
The JSON MUST validate against schemas/capability-map.schema.json.
Workflow (MANDATORY order):
- WRITE PLACEHOLDER (your first action - see above)
- READ the spec from
{TASKER_DIR}/inputs/spec.md - ANALYZE using I.P.S.O. decomposition (see below)
- OVERWRITE the file with your complete analysis using the Write tool
- VALIDATE:
cd {TASKER_DIR}/.. && tasker state validate capability_map - If validation fails: Fix the JSON, Write again, re-validate
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.
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 · 285 lines · 25 tokens per session scan A 25058e40d9be
logic-architect is an agent published in the GitHub repository Dowwie/tasker (19 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 25 tokens to every session and 2,362 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.
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".