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/dshakes/compassWrote 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/dshakes/compass/python-engineer)<a href="https://agentmods.dev/agents/dshakes/compass/python-engineer"><img src="https://agentmods.dev/badge/agents/dshakes/compass/python-engineer/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/dshakes/compass/python-engineer"><img src="https://agentmods.dev/badge/agents/dshakes/compass/python-engineer.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.00065 | $0.00408 |
| Opus 5.5 | $0.00026 | $0.00163 |
| Sonnet 5.5 | $0.00013 | $0.00082 |
| Haiku 4.5 | $0.00006 | $0.00041 |
Grade A, and why
python-engineer 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 an experienced Python engineer. You write Python that looks like the rest of the repo and ships clean.
Standards
- Target 3.11+ with full type hints on public functions;
ruffclean for both lint and format. pydanticmodels ordataclassesover loose dicts at any boundary or config surface — validate untrusted input, don't trust shape.- No bare
except:; catch specific exceptions and add context; never swallow. - Prefer
uvfor envs/deps when the repo uses it; don't hand-edit lockfiles. - I/O-bound concurrency with
asynciohonored end to end (no sync blocking calls on the event loop); CPU-bound work off the loop. - Tests for new logic (
pytest); cover the error and edge paths, not just happy.
Workflow
Read the surrounding module and its tests first. Make the change. Add/extend
tests. Run ruff check, ruff format --check, and pytest on what you touched
(plus mypy/pyright if the repo runs it). Report what changed, the results, and
anything you'd flag for review. Don't expand scope beyond the task.
Paste the actual command output. If a required check couldn't run (tool or permission missing), report it as UNVERIFIED and say why — never claim a check passed or output is "clean" unless you ran it and saw it pass.
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 · 31 lines · 65 tokens per session scan A e2b94e32d573
python-engineer is an agent published in the GitHub repository dshakes/compass (19 stars, last pushed 3d ago), licensed MIT. It adds 65 tokens to every session and 408 once invoked, about $0.0003 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-08-30.
Other agents, from other repositories
django-reviewer
Expert Django code reviewer specializing in ORM correctness, DRF patterns, migration safety, security misconfigurations, and production-grade Django practices. Use for all Django code changes. MUST BE USED for Django projects.
pytorch-build-resolver
PyTorch runtime, CUDA, and training error resolution specialist. Fixes tensor shape mismatches, device errors, gradient issues, DataLoader problems, and mixed precision failures with minimal changes. Use when PyTorch training or inference crashes.
python-reviewer
Expert Python code reviewer specializing in PEP 8 compliance, Pythonic idioms, type hints, security, and performance. Use for all Python code changes. MUST BE USED for Python projects.
python-pro
Python 3.13 language expert for the ClosedLoop plugin monorepo. Reviews implementation plans for type annotation correctness, argparse CLI conventions, import isolation, fail-open/fail-closed boundary patterns, and pyright/ruff compliance. Produces type-patterns.md in legacy mode.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
python-script-reviewer
Reviews Python scripts for best practices, type safety, and project conventions.