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.
git clone --depth 1 https://github.com/iloveitaly/llm-ide-rulesWrote 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/iloveitaly/llm-ide-rules/fix-tests)<a href="https://agentmods.dev/commands/iloveitaly/llm-ide-rules/fix-tests"><img src="https://agentmods.dev/badge/commands/iloveitaly/llm-ide-rules/fix-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.1 | $0.00000 | $0.00274 |
| Opus 5 | $0.00000 | $0.00137 |
| Sonnet 5 | $0.00000 | $0.00055 |
| Haiku 4.5 | $0.00000 | $0.00027 |
Grade A, and why
fix-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 8d 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 Tests
Focus on all unit + command tests (pytest --exclude tests/integration). Make sure they pass and fix errors. If you run into anything very odd: stop, and let me know. Mutate test code first and let me know if you think you should update application code.
Then, focus on integration tests in tests/integration. If an integration test fails, run it again just to be sure it wasn't a flakey test (integration tests are not deterministic). If it fails because of a visual error, check the 'tmp/test-results/playwright/' directory for a screenshot relating to the failing test that you can inspect.
For additional debugging help, view the development version of the site at $PYTHON_TEST_SERVER_HOST using a browser.
Do not attempt to perform this task in a sandbox. Service connections require access to host networking.
If you get stuck or seem to be in a loop, give me a short summary of exactly where you are running into trouble, let me know, and stop working.
Do not attempt to solve these issues:
just,direnv, andjs_buildshould always run or exist.- Chromium/Chrome/playwright not working properly.
- Postgres, Redis, or other service connection errors.
If you run into errors, stop immediately and let me know with a summary of the problem.
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.
- 8d ago First seen · 20 lines · 0 tokens per session scan A 7ef7d1500789
fix-tests is a command published in the GitHub repository iloveitaly/llm-ide-rules (13 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 274 tokens. 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-30.
Other commands, from other repositories
run_tests
Use the text the user typed after the command name as the request for this command.
implement_tests
Use the text the user typed after the command name as the request for this command.
AGENTS
Commander.js-based CLI commands registered in src/main.ts.
testgen-flow-data-collection
Phase 1 Data Collection of testgen-flow.
testgen-flow-gap-and-contradiction-analysis
Phase 2 Gap & Contradiction Analysis of testgen-flow.
testgen-flow-requirements-document-generation
Phase 4 Requirements Document of testgen-flow.