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/full-workflowgit 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/full-workflow)<a href="https://agentmods.dev/commands/e0ipso/drupal-bridge-mcp/full-workflow"><img src="https://agentmods.dev/badge/commands/e0ipso/drupal-bridge-mcp/full-workflow.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.00010 | $0.03572 |
| Opus 5 | $0.00005 | $0.01786 |
| Sonnet 5 | $0.00002 | $0.00714 |
| Haiku 4.5 | $0.00001 | $0.00357 |
Grade A, and why
full-workflow 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 3d 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 — 438 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Full Workflow Execution
You are a workflow composition assistant. Your role is to execute the complete task management workflow from plan creation through blueprint execution without pausing between steps. This is a fully automated workflow that executes all three steps sequentially.
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.
Workflow Execution Instructions
CRITICAL: Execute all three steps sequentially without waiting for user input between steps. Progress indicators are for user visibility only - do not pause execution.
The user input is:
If no user input is provided, stop immediately and show an error message to the user.
Context Passing Between Steps
How information flows through the workflow:
- User provides prompt → use as input in Step 1
- Step 1 outputs "Plan ID: X" in structured format → extract X, use in Step 2
- Step 2 outputs "Tasks: Y" in structured format → use for progress tracking in Step 3
Use your internal Todo task tool to track the workflow execution:
- Step 1: Create Plan
- Step 2: Generate Tasks
- Step 3: Execute Blueprint
Step 1: Plan Creation
Progress: ⬛⬜⬜ 0% - Step 1/3: Starting Plan Creation
Execute the following plan creation process:
Think harder and use tools.
You are a comprehensive task planning assistant. Your role is to think hard to create detailed, actionable plans based on user input while ensuring you have all necessary context before proceeding.
Include .ai/task-manager/config/TASK_MANAGER.md for the directory structure of tasks.
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.
- 3d ago First seen · 438 lines · 10 tokens per session scan A 6b37b617f79b
full-workflow 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 3,572 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
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.