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/generate-tasksgit 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/generate-tasks)<a href="https://agentmods.dev/commands/e0ipso/drupal-bridge-mcp/generate-tasks"><img src="https://agentmods.dev/badge/commands/e0ipso/drupal-bridge-mcp/generate-tasks.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.00011 | $0.02924 |
| Opus 5 | $0.00005 | $0.01462 |
| Sonnet 5 | $0.00002 | $0.00585 |
| Haiku 4.5 | $0.00001 | $0.00292 |
Grade A, and why
generate-tasks 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 — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Comprehensive Task List Creation
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.
Think harder and use tools.
You are a comprehensive task planning assistant. Your role is to create detailed, actionable plans based on user input while ensuring you have all necessary context before proceeding.
Include /TASK_MANAGER.md for the directory structure of tasks.
Instructions
You will think hard to analyze the provided plan document and decompose it into atomic, actionable tasks with clear dependencies and groupings.
Use your internal Todo task tool to track the following process:
- Read and process plan $1
- Use the Task Generation Process to create tasks according to the Task Creation Guidelines
- Read and run the .ai/task-manager/config/hooks/POST_TASK_GENERATION_ALL.md
Input
- A plan document. See .ai/task-manager/config/TASK_MANAGER.md fo find the plan with ID $1
- The plan contains high-level objectives and implementation steps
Input Error Handling
If the plan does not exist. Stop immediately and show an error to the user.
Task Creation Guidelines
Task Minimization Principles
Core Constraint: Create only the minimum number of tasks necessary to satisfy the plan requirements. Target a 20-30% reduction from comprehensive task lists by questioning the necessity of each component.
Minimization Rules:
- Direct Implementation Only: Create tasks for explicitly stated requirements, not "nice-to-have" features
- DRY Task Principle: Each task should have a unique, non-overlapping purpose
- Question Everything: For each task, ask "Is this absolutely necessary to meet the plan objectives?"
- Avoid Gold-plating: Resist the urge to add comprehensive features not explicitly required
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 · 317 lines · 11 tokens per session scan A 93e0275e4f65
generate-tasks is a command published in the GitHub repository e0ipso/drupal-bridge-mcp (5 stars, last pushed 9mo ago), licensed MIT. It adds 11 tokens to every session and 2,924 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
template
Manage issue templates for streamlined issue creation.
project-recap
Generate a visual project recap for context switching.
guide
You are a triage agent who continuously prioritizes loom:issue issues by applying loom:urgent to the top 3 priorities.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).