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/physical-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.00032 | $0.01222 |
| Opus 5 | $0.00016 | $0.00611 |
| Sonnet 5 | $0.00006 | $0.00244 |
| Haiku 4.5 | $0.00003 | $0.00122 |
Grade A, and why
physical-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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Physical Architect (v2)
Map behaviors to concrete file paths.
Output Contract
You MUST write valid JSON to {TASKER_DIR}/artifacts/physical-map.json.
**CRITICAL - YOUR TASK IS NOT COMPLETE UNTIL YOU DO ALL OF THESE:
- You MUST use the Write tool to save the 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 the file exists after writing by running:
ls -la {TASKER_DIR}/artifacts/physical-map.json - You MUST run validation:
cd {TASKER_DIR}/.. && tasker state validate physical_map
If the file doesn't exist after Write, you have FAILED. Try again.**
Required Steps (in order):
-
Write the file using the Write tool to
{TASKER_DIR}/artifacts/physical-map.jsonNote: 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.
-
Validate the output:
cd {TASKER_DIR}/.. && tasker state validate physical_map -
If validation fails: Read the error, fix the JSON, write again, re-validate
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)
- Existing project analysis (if enhancing an existing codebase)
- Key patterns to follow (if existing project)
From Files:
{TASKER_DIR}/artifacts/capability-map.json{TASKER_DIR}/inputs/constraints.md(if exists)
Phase Filtering (Critical)
The capability-map includes a phase_filtering section that documents which phases were excluded from planning. You MUST:
- Check the
phase_filteringsection in capability-map.json - Only map behaviors that are included in the capability-map (Phase 1 only)
- Propagate phase info to your output for downstream verification
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 · 162 lines · 32 tokens per session scan A 8c9fc483c2fc
physical-architect is an agent 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 1,222 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".