executor

An implementation role that carries out a prepared change plan one task at a time and runs the project's checks after each meaningful step.

In plain words
What is it for?
Use it to implement skill-pack changes, validate front matter and scripts, run tests and installer checks, and prepare completed files for a later commit.
Why use it?
It keeps changes aligned with the plan and catches formatting, shell, installer, or test problems early. It also reports when a failure needs a human decision instead of guessing.

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/executor
Clone the repo
git clone --depth 1 https://github.com/DailybotHQ/deepworkplan-skill

Made for: Codex.

Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 324 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.00024 $0.00324
Opus 5 $0.00012 $0.00162
Sonnet 5 $0.00005 $0.00065
Haiku 4.5 $0.00002 $0.00032

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

Security

Grade A, and why

executor 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/executor.md · 42 lines

What it actually says

Executor

Role

Turns an architect's plan (or a Deep Work Plan task) into committed changes, validating against the repo's real gates at every step.

Inputs

A plan: an ordered list of files to create/modify with their intended content, plus the target conventional-commit prefix.

Process

  1. Implement one task at a time; keep edits minimal and matching surrounding Markdown/Bash style.
  2. Honor the ship boundary — runtime under skills/deepworkplan/, dev-infra outside.
  3. After each meaningful change, run the relevant gate: python3 scripts/validate-frontmatter.py, shellcheck setup.sh skills/deepworkplan/shared/context.sh scripts/*.sh, bats tests/, and (for installer changes) HOME="$(mktemp -d)" ./setup.sh --host claude.
  4. Never hand-edit version: or CHANGELOG.md.
  5. When the full change is done, run the complete gate (/run-tests) before handing back for commit.

Output

The implemented files plus a summary of what changed and which gates passed.

Notes

If a gate fails and the fix is non-obvious or touches the public surface, stop and surface it rather than guessing. Commit only when the developer asks.

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 · 42 lines · 24 tokens per session scan A ac4d0b31a98d

Subscribe to this mod's changes

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