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 commands/e0ipso/drupal-bridge-mcp/execute-taskgit clone --depth 1 https://github.com/e0ipso/drupal-bridge-mcpWhat 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.00010 | $0.01762 |
| Opus 5 | $0.00005 | $0.00881 |
| Sonnet 5 | $0.00002 | $0.00352 |
| Haiku 4.5 | $0.00001 | $0.00176 |
Grade A, and why
execute-task 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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Single Task Execution
You are responsible for executing a single task within a plan while maintaining strict dependency validation and proper status management. Your role is to ensure the task is ready for execution, deploy the appropriate agent, and track execution progress.
Use your internal Todo task tool to track the execution of all parts of the task, and the final update of noteworthy items during execution. Example:
- Validate task: file, status, and dependencies.
- Select the most appropriate sub-agent.
- Set task status to in-progress.
- Delegate task implementation to the sub-agent.
- Update task status to completed or failed.
- Update the task file with noteworthy events during execution.
Critical Rules
- Never skip dependency validation - Task execution requires all dependencies to be completed
- Validate task status - Never execute tasks that are already completed or in-progress
- Maintain status integrity - Update task status throughout the execution lifecycle
- Use appropriate agents - Match task skills to available sub-agents
- Document execution - Record all outcomes and issues encountered
Input Requirements
- Plan ID: $1 (required)
- Task ID: $2 (required)
- Task management directory structure:
/ - Dependency checking script:
.ai/task-manager/config/scripts/check-task-dependencies.cjs
Input Validation
First, validate that both arguments are provided:
if [ -z "$1" ] || [ -z "$2" ]; then
echo "Error: Both plan ID and task ID are required"
echo "Usage: /tasks:execute-task [plan-ID] [task-ID]"
echo "Example: /tasks:execute-task 16 03"
exit 1
fi
Execution Process
1. Plan and Task Location
Locate the plan directory using the established find pattern:
PLAN_ID="$1"
TASK_ID="$2"
# Find plan directory
PLAN_DIR=$(find .ai/task-manager/{plans,archive} -type d -name "${PLAN_ID}--*" 2>/dev/null | head -1)
if [ -z "$PLAN_DIR" ]; then
echo "Error: Plan with ID ${PLAN_ID} not found"
echo "Available plans:"
find .ai/task-manager/plans -name "*--*" -type d | head -5
exit 1
fi
echo "Found plan: $PLAN_DIR"
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 · 259 lines · 0 tokens per session scan A ec3492bedebe
execute-task is a command published in the GitHub repository e0ipso/drupal-bridge-mcp (5 stars, last pushed 9mo ago), licensed MIT. It adds 10 tokens to every session and 1,762 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-31.
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.