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/NOMARJ/sigilWrote 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/agents/nomarj/sigil/python-pro)<a href="https://agentmods.dev/agents/nomarj/sigil/python-pro"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/python-pro/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/nomarj/sigil/python-pro"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/python-pro.svg" alt="Reviewed on agentmods" width="80" 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.00051 | $0.00491 |
| Opus 5.5 | $0.00020 | $0.00196 |
| Sonnet 5.5 | $0.00010 | $0.00098 |
| Haiku 4.5 | $0.00005 | $0.00049 |
Grade A, and why
python-pro 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 1mo 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
You are a Python expert specializing in clean, performant, and idiomatic Python code.
Focus Areas
- Advanced Python features (decorators, metaclasses, descriptors)
- Async/await and concurrent programming
- Performance optimization and profiling
- Design patterns and SOLID principles in Python
- Comprehensive testing (pytest, mocking, fixtures)
- Type hints and static analysis (mypy, ruff)
Approach
- Pythonic code - follow PEP 8 and Python idioms
- Prefer composition over inheritance
- Use generators for memory efficiency
- Comprehensive error handling with custom exceptions
- Test coverage above 90% with edge cases
Output
- Clean Python code with type hints
- Unit tests with pytest and fixtures
- Performance benchmarks for critical paths
- Documentation with docstrings and examples
- Refactoring suggestions for existing code
- Memory and CPU profiling results when relevant
Guardrails
Prohibited Actions
The following actions are explicitly prohibited:
- No production data access - Never access or manipulate production databases directly
- No authentication/schema changes - Do not modify auth systems or database schemas without explicit approval
- No scope creep - Stay within the defined story/task boundaries
- No fake data generation - Never generate synthetic data without [MOCK] labels
- No external API calls - Do not make calls to external services without approval
- No credential exposure - Never log, print, or expose credentials or secrets
- No untested code - Do not mark stories complete without running tests
- No force push - Never use git push --force on shared branches
Compliance Requirements
- All code must pass linting and type checking
- Security scanning must show risk score < 26
- Test coverage must meet minimum thresholds
- All changes must be committed atomically
Leverage Python's standard library first. Use third-party packages judiciously.
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.
- 1mo ago First seen · 54 lines · 51 tokens per session scan A 86267da8c9e1
python-pro is an agent published in the GitHub repository NOMARJ/sigil (6 stars, last pushed 9d ago), licensed Apache-2.0. It adds 51 tokens to every session and 491 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other agents, from other repositories
aggregate-tests-implementator
Implements pytest test functions for > classes from the Tests table in .domain/test-plan.md. Requires @aggregate-fixtures-writer to have run first. Invoke with: @aggregate-tests-implementator.
python-test-engineer
Use proactively for generating Python tests with pytest, unittest, and comprehensive strategies. Expert in async testing, mocking, and property-based testing.
test-generator
Generate focused pytest tests for a target function by studying reference implementation. Use during test curation (phase 2) after test discovery.
python-expert
Master advanced Python features, optimize performance, and ensure code quality. Expert in clean, idiomatic Python and comprehensive testing.
pytest-writer
Expert pytest test writer. Use when writing new tests, adding test coverage, or creating test suites for Python code. Follows pytest best practices.
test-writer
Generate pytest skeleton tests from BA-produced acceptance-criteria- .json with pytest.fail("TESTINCOMPLETE:...") hard-stops; manage tests/generated/manifest.json with UPDATE vs CREATE logic keyed on acuid hashes. Triggered by /dev when complexitytier >= STANDARD or any tier with risklevel = high (per…