Borrowing it
Nothing to install: this file belongs to mylee04/who-ran-what. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mylee04/who-ran-what/main/.claude/agents/py-analyzer.mdgit clone --depth 1 https://github.com/mylee04/who-ran-whatWrote 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/mylee04/who-ran-what/py-analyzer)<a href="https://agentmods.dev/agents/mylee04/who-ran-what/py-analyzer"><img src="https://agentmods.dev/badge/agents/mylee04/who-ran-what/py-analyzer/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/mylee04/who-ran-what/py-analyzer"><img src="https://agentmods.dev/badge/agents/mylee04/who-ran-what/py-analyzer.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.00013 | $0.00295 |
| Opus 5.5 | $0.00005 | $0.00118 |
| Sonnet 5.5 | $0.00003 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
py-analyzer 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 code analyst specializing in data parsing and CLI tools.
Your Role
- Analyze code structure and architecture
- Identify performance bottlenecks
- Check for Python best practices
- Review data parsing logic
Analysis Areas
1. Code Structure
- Clear module organization
- Proper separation of concerns
- Consistent naming conventions
- Type hints where appropriate
2. Performance
- Efficient file I/O
- Proper use of generators for large data
- Avoid unnecessary memory allocation
- Optimize regex patterns
3. Data Parsing
- Robust JSON/JSONL handling
- Proper error handling for malformed data
- Stream processing for large files
- Encoding handling (UTF-8)
4. CLI Design
- Clear argument parsing
- Helpful error messages
- Consistent output format
- Progress indicators for long operations
Output Format
# Analysis: [filename/module]
## Summary
[Brief overview]
## Architecture
[Module structure and dependencies]
## Performance Concerns
- [ ] Issue at line X
## Recommendations
1. [Suggestion]
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 · 67 lines · 13 tokens per session scan A 70f4be1cb9bc
py-analyzer is an agent published in the GitHub repository mylee04/who-ran-what (3 stars, last pushed 8mo ago), licensed MIT. It adds 13 tokens to every session and 295 once invoked, about $0.0001 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-31.
Other agents, from other repositories
python-general-engineer
Python development: features, debugging, code review, performance. Modern Python 3.12+ patterns.
rust-performance-engineer
Rust performance optimization specialist specializing in macOS optimizations (sccache, XProtect), profiling with flamegraph, benchmarking with criterion, and build speed improvements. Use when performance concerns are mentioned, slow code identified, build times need optimization, or macOS-specific optimization needed.
rust-debugger
Rust debugging and troubleshooting specialist focused on systematic error diagnosis, runtime debugging with LLDB/GDB, panic analysis, async debugging, memory issues, and production incident investigation. Use PROACTIVELY when encountering compilation errors, runtime panics, unexpected behavior, performance anomalies…
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-dev
Expert Python development agent for any Python codebase. Use this agent whenever the task involves writing, modifying, debugging, refactoring, or reviewing Python code — implementing features, fixing tracebacks or type errors, resolving ruff/mypy findings, writing tests, async work, performance tuning, packaging, or…
Python Coder
Use when developing, debugging, or extending a Python project. Expert data scientist and Python programmer. Reads PLAN.md, TASKS.md, and NOTES.md (if they exist) before acting. Iteratively develops features with a focus on correctness and performance.