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-blueprintgit clone --depth 1 https://github.com/e0ipso/drupal-bridge-mcpWrote 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/e0ipso/drupal-bridge-mcp/execute-blueprint)<a href="https://agentmods.dev/commands/e0ipso/drupal-bridge-mcp/execute-blueprint"><img src="https://agentmods.dev/badge/commands/e0ipso/drupal-bridge-mcp/execute-blueprint.svg" alt="Measured on agentmods" 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 | $0.00006 | $0.04527 |
| Opus 5 | $0.00003 | $0.02263 |
| Sonnet 5 | $0.00001 | $0.00905 |
| Haiku 4.5 | $0.00001 | $0.00453 |
Grade A, and why
execute-blueprint 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 4d 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 — 478 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Execution
Assistant Configuration
Before proceeding with this command, you MUST load and respect the assistant's configuration:
Run the following scripts:
ASSISTANT=$(node .ai/task-manager/config/scripts/detect-assistant.cjs)
node .ai/task-manager/config/scripts/read-assistant-config.cjs "$ASSISTANT"
The output above contains your global and project-level configuration rules. You MUST keep these rules and guidelines in mind during all subsequent operations in this command.
You are the coordinator responsible for executing all tasks defined in the execution blueprint of a plan document, so choose an appropriate sub-agent for this role. Your role is to coordinate phase-by-phase execution, manage parallel task processing, and ensure validation gates pass before phase transitions.
Critical Rules
- Never skip validation gates - Phase progression requires successful validation
- Maintain task isolation - Parallel tasks must not interfere with each other
- Preserve dependency order - Never execute a task before its dependencies
- Document everything - All decisions, issues, and outcomes must be recorded in the "Execution Summary", under "Noteworthy Events"
- Fail safely - Better to halt and request help than corrupt the execution state
Input Requirements
- A plan document with an execution blueprint section. See /TASK_MANAGER.md fo find the plan with ID $1
- Task files with frontmatter metadata (id, group, dependencies, status)
- Validation gates document:
/config/hooks/POST_PHASE.md
Input Error Handling
If the plan does not exist, stop immediately and show an error to the user.
Note: If tasks or the execution blueprint section are missing, they will be automatically generated before execution begins (see Task and Blueprint Validation below).
Task and Blueprint Validation
Before proceeding with execution, validate that tasks exist and the execution blueprint has been generated. If either is missing, automatically invoke task generation.
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.
- 4d ago First seen · 478 lines · 6 tokens per session scan A 6e088b0cc026
execute-blueprint is a command published in the GitHub repository e0ipso/drupal-bridge-mcp (5 stars, last pushed 9mo ago), licensed MIT. It adds 6 tokens to every session and 4,527 once invoked, about $0.0000 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
git
Git operations with intelligent commit messages and workflow optimization.
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.