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/fix-broken-testsgit 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/fix-broken-tests)<a href="https://agentmods.dev/commands/e0ipso/drupal-bridge-mcp/fix-broken-tests"><img src="https://agentmods.dev/badge/commands/e0ipso/drupal-bridge-mcp/fix-broken-tests.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.00008 | $0.00293 |
| Opus 5 | $0.00004 | $0.00147 |
| Sonnet 5 | $0.00002 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
fix-broken-tests 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.
What it actually says
Fix all failing tests in this repository. Think harder and use tools.
Execute this command to run the tests:
If the test command is empty, read CLAUDE.md for test execution instructions.
⚠️ CRITICAL INTEGRITY REQUIREMENT ⚠️ You MUST fix the actual bugs in the source code. Green tests are worthless if achieved through cheating.
This is CHEATING (absolutely forbidden):
- Skipping tests with conditionals
- Modifying test assertions to pass
- Adding test-environment-specific code to source
- Disabling or commenting out tests
- ANY workaround that doesn't fix the real bug
This is THE RIGHT WAY:
- Find the root cause in the source code
- Fix the actual bug
- Ensure tests pass because the code truly works
Process:
- Run all tests to identify failures
- Fix EVERY failing test iteratively
- Verify all tests pass legitimately
DO NOT STOP after fixing some tests - fix ALL of them.
Remember: The entire point of tests is to ensure code robustness. If you cheat in ANY way, the tests become meaningless and I cannot trust that the code actually works.
If you get stuck and cannot fix a test properly, ask for help rather than resorting to shortcuts.
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 · 39 lines · 8 tokens per session scan A 1fd2992bd046
fix-broken-tests is a command published in the GitHub repository e0ipso/drupal-bridge-mcp (5 stars, last pushed 10mo ago), licensed MIT. It adds 8 tokens to every session and 293 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
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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.