architect

A planning role for changes to a software skill pack. It decides where new skills, add-ons, or presets belong and what metadata and version change they need.

In plain words
What is it for?
Use it before adding a sub-skill, add-on, preset, command, or other structural change to plan the files, routing, front matter, and release version.
Why use it?
It prevents new additions from being placed in the wrong part of the pack or shipped without the required structure and documentation.

Agent for Codex

Install

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.

agentmods
npx agentmods add agents/dailybothq/deepworkplan-skill/architect
Clone the repo
git clone --depth 1 https://github.com/DailybotHQ/deepworkplan-skill

Made for: Codex.

Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 471 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00029 $0.00471
Opus 5 $0.00015 $0.00235
Sonnet 5 $0.00006 $0.00094
Haiku 4.5 $0.00003 $0.00047

Measured 2d ago against content hash 5ff8e654318c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

.agents/agents/architect.md · 47 lines

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

  1. Classify the change against the ship boundary: is it runtime (under skills/deepworkplan/) or dev-infra (root/.agents//.github/)?
  2. Pick the location by analogy to existing structure — a new sub-skill is a folder with its own SKILL.md; an addon lives under skills/deepworkplan/addons/<name>/; a preset under onboard/presets/. Consult docs/SUB_SKILL_GUIDE.md for the sub-skill recipe.
  3. Define the frontmatter (name: deepworkplan-<thing>, quoted version:, documentation_url:, user-invocable, allowed-tools) and whether it adds a /deepworkplan-* slash command.
  4. Determine the bump level: new sub-skill/addon/preset → MINOR (feat); renamed command / changed .dwp/ convention / removed surface → MAJOR (feat!); internal/docs → PATCH.
  5. 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.

Changes

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.

  1. 2d ago First seen · 47 lines · 29 tokens per session scan A 5ff8e654318c

Subscribe to this mod's changes

architect is an agent published in the GitHub repository DailybotHQ/deepworkplan-skill (20 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 471 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.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens