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/iloveitaly/llm-ide-rules/standalone-python-scriptsgit clone --depth 1 https://github.com/iloveitaly/llm-ide-rulesWhat 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.00000 | $0.00285 |
| Opus 5 | $0.00000 | $0.00143 |
| Sonnet 5 | $0.00000 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
standalone-python-scripts 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 2d 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
Standalone Python Scripts
Use this header:
#!/usr/bin/env -S uv run --script
# /// script
# requires-python = ">=3.13"
# dependencies = []
# ///
- Specify dependencies via the
dependenciesvariable in the above comment - Do not install packages with pip or any other package manager, assume packages will be installed when needed using
uv run --script. - Use
clickfor CLI interfaces - When listing constants at the top of the file, include a newline between entries and (for non-obvious constants) document each constant with a comment:
# matches full lowercase git shas (short or full)
SHA_REGEX = re.compile(r"^[0-9a-f]{7,40}$")
# matches any char not allowed in dns labels
SAFE_CHARS_REGEX = re.compile(r"[^a-z0-9-]")
DEFAULT_ENVIRONMENT_NAME = "production"
DEFAULT_SERVICE_NAME = "Postgres"
CLI Output and Logging
- Use
structlog_configfor logging. Read the usage guide: @https://github.com/iloveitaly/structlog-config/ - Use logging for operational/debugging info that goes to structured logs.
- Use CLI output for user-facing messages the user needs to see during normal execution (status updates, warnings, errors). Color these messages.
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.
- 2d ago First seen · 34 lines · 0 tokens per session scan A cc89667b0cc2
standalone-python-scripts is a command published in the GitHub repository iloveitaly/llm-ide-rules (13 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 285 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
code-review
Perform a thorough code review that verifies functionality, maintainability, and security before approving a change. Focus on architecture, readability, performance implications, and provide actionable suggestions for improvement.
add-documentation
Add comprehensive documentation for the current code/feature and format it according to the project's documentation standards, including it in the appropriate location (README, docs folder, or inline comments).
add-error-handling
Implement comprehensive error handling for the current code to make it robust and resilient to failures while maintaining good user experience.
optimize-performance
Analyze the current code for performance bottlenecks and provide optimization recommendations, focusing on measurable improvements while maintaining code quality and readability.
write-unit-tests
Create comprehensive unit tests for the current code and generate the test file with proper imports and setup according to the project's testing conventions.
project-overview
High-level overview of the project to help quickly understand what it is, how it is structured, and how to run it locally.