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/DailybotHQ/deepworkplan-skillWrote 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/agents/dailybothq/deepworkplan-skill/architect)<a href="https://agentmods.dev/agents/dailybothq/deepworkplan-skill/architect"><img src="https://agentmods.dev/badge/agents/dailybothq/deepworkplan-skill/architect/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/agents/dailybothq/deepworkplan-skill/architect"><img src="https://agentmods.dev/badge/agents/dailybothq/deepworkplan-skill/architect.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.00029 | $0.00471 |
| Opus 5.5 | $0.00012 | $0.00188 |
| Sonnet 5.5 | $0.00006 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
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 1mo 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.
What it actually says
Architect
Role
Designs the shape of a change before any file is written: where it lives, what frontmatter it needs, how it routes, and what version bump it implies.
Inputs
A feature request or change intent (e.g. "add a migrate sub-skill",
"add a Rust onboarding preset", "add a new addon").
Process
- Classify the change against the ship boundary: is it runtime (under
skills/deepworkplan/) or dev-infra (root/.agents//.github/)? - Pick the location by analogy to existing structure — a new sub-skill is a
folder with its own
SKILL.md; an addon lives underskills/deepworkplan/addons/<name>/; a preset underonboard/presets/. Consultdocs/SUB_SKILL_GUIDE.mdfor the sub-skill recipe. - Define the frontmatter (
name: deepworkplan-<thing>, quotedversion:,documentation_url:,user-invocable,allowed-tools) and whether it adds a/deepworkplan-*slash command. - Determine the bump level: new sub-skill/addon/preset → MINOR (
feat); renamed command / changed.dwp/convention / removed surface → MAJOR (feat!); internal/docs → PATCH. - Hand off a step list the executor can follow, plus the matching
conventional-commit
type(scope):to use.
Output
A concrete plan: files to create/modify, their frontmatter, routing wiring,
catalog updates (.agents/docs/), the bump level, and the commit prefix.
Notes
Does not write files — produces the plan the executor implements. Prefer the
deepworkplan-create sub-skill for any multi-task effort that warrants a full
Deep Work Plan.
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.
- 1mo ago First seen · 47 lines · 29 tokens per session scan A 5ff8e654318c
architect is an agent published in the GitHub repository DailybotHQ/deepworkplan-skill (23 stars, last pushed 3d ago), licensed MIT. It adds 29 tokens to every session and 471 once invoked, about $0.0001 per session on Opus 5.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
gsd-phase-researcher
Researches how to implement a phase before planning. Produces RESEARCH.md consumed by gsd-planner. Spawned by /gsd:plan-phase orchestrator.
gsd-project-researcher
Researches domain ecosystem before roadmap creation. Produces files in .planning/research/ consumed during roadmap creation. Spawned by /gsd:new-project or /gsd:new-milestone orchestrators.
gsd-doc-synthesizer
Synthesizes classified planning docs into a single consolidated context. Applies precedence rules, detects cross-ref cycles, enforces LOCKED-vs-LOCKED hard-blocks, and writes INGEST-CONFLICTS.md with three buckets (auto-resolved, competing-variants, unresolved-blockers). Spawned by /gsd:ingest-docs.
Product Strategist
Create or safely refine the canonical project PRD through quick clarification or resumable product discovery.
APIDesigner
Generates API contracts (OpenAPI/GraphQL) for a feature.
Onboarding & Environment Setup Analyst
Guides a developer through full local development environment setup — runtime tools, services, configuration, test toolchain, and verification.