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.
git clone --depth 1 https://github.com/ils15/pantheon-legacyWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/ils15/pantheon-legacy/pantheon-deepwork)<a href="https://agentmods.dev/commands/ils15/pantheon-legacy/pantheon-deepwork"><img src="https://agentmods.dev/badge/commands/ils15/pantheon-legacy/pantheon-deepwork/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/ils15/pantheon-legacy/pantheon-deepwork"><img src="https://agentmods.dev/badge/commands/ils15/pantheon-legacy/pantheon-deepwork.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00042 | $0.00909 |
| Opus 5 | $0.00021 | $0.00454 |
| Sonnet 5 | $0.00008 | $0.00182 |
| Haiku 4.5 | $0.00004 | $0.00091 |
Grade A, and why
pantheon-deepwork 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 9d 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.
This is a copy
95% identical to deepwork — 20 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pantheon-deepwork — Heavy Task Workflow
What: Starts a structured, checkpointed workflow for complex multi-step tasks. Progress is persisted to .pantheon/deepwork/<task-slug>/ so work can resume if interrupted. Each phase is gated by Themis review.
When to Use
- Tasks expected to take 10+ turns
- Multi-agent orchestration with dependencies
- Work that spans multiple sessions
- Anything where losing context mid-way would be costly
When NOT to Use
- Simple fixes (use @talos)
- Single-file changes (use /subtask)
- Tasks completable in < 5 turns (use normal delegation)
Workflow
Phase 0: SCOPING
└─ Zeus + Athena define task scope, phases, and acceptance criteria
└─ Output: .pantheon/deepwork/<slug>/PLAN.md
Phase 1: DISCOVERY
└─ @apollo maps relevant codebase areas
└─ Output: .pantheon/deepwork/<slug>/DISCOVERY.md
Phase 2-N: IMPLEMENTATION (parallel per phase)
└─ @hermes / @aphrodite / @demeter implement phase scope
└─ Output: .pantheon/deepwork/<slug>/phase-<N>-<agent>.md
GATE after each phase:
└─ @themis reviews phase output
└─ FAIL → fix and re-submit
└─ PASS → continue to next phase
Phase FINAL: VERIFICATION
└─ @themis full integration review
└─ All tests pass, coverage >80%
└─ Output: .pantheon/deepwork/<slug>/REVIEW.md
Checkpoint System
Each phase writes a checkpoint file. If work is interrupted:
/pantheon-deepwork --resume <slug> # Resume from last checkpoint
/pantheon-deepwork --status <slug> # Show current progress
/pantheon-deepwork --list # List all deepwork tasks
Checkpoint files:
.pantheon/deepwork/<slug>/
├── PLAN.md # Scope and phase plan
├── DISCOVERY.md # Codebase map
├── phase-1-hermes.md # Phase 1 backend work
├── phase-1-aphrodite.md # Phase 1 frontend work
├── phase-1-review.md # Phase 1 Themis review
├── phase-2-*.md # Subsequent phases
├── REVIEW.md # Final Themis review
└── STATUS.md # Current state (phase, progress, blockers)
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.
- 9d ago First seen · 102 lines · 42 tokens per session scan A 73fc34fadaa1
pantheon-deepwork is a command published in the GitHub repository ils15/pantheon-legacy (10 stars, last pushed 6d ago), licensed MIT. It adds 42 tokens to every session and 909 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to deepwork, differing in 20 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.