who-ran-what: Agent for Claude Code

.claude/agents/py-analyzer.md

py-analyzer is an agent for Claude Code from mylee04/who-ran-what. It costs 13 tokens per session (295 once invoked), scanned A, original, MIT.

An analyst for Python code, the programming language, that reviews how the code is organised, how it handles data, and how efficiently it runs. It also examines command-line design and parsing logic.

In plain words
What is it for?
Reviewing Python modules, file and JSON parsing, regular expressions, memory use, type hints, and CLI behaviour.
Why use it?
It helps identify unclear structure, slow operations, fragile data handling, and other maintainability problems.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

This is mylee04/who-ran-what's own configuration. It tells Claude Code how to work on who-ran-what itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything who-ran-what configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/mylee04/who-ran-what/main/.claude/agents/py-analyzer.md
Clone the repo
git clone --depth 1 https://github.com/mylee04/who-ran-what

Made for: Claude Code.

Wrote 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.

agentmods badge for py-analyzer

README.md
[![agentmods](https://agentmods.dev/badge/agents/mylee04/who-ran-what/py-analyzer/github.svg)](https://agentmods.dev/agents/mylee04/who-ran-what/py-analyzer)
Your own site
<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.

agentmods 80×15 button for py-analyzer

Your own site · 80×15
<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>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 295 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00013 $0.00295
Opus 5 $0.00006 $0.00148
Sonnet 5 $0.00003 $0.00059
Haiku 4.5 $0.00001 $0.00030

Measured 9d ago against content hash 70f4be1cb9bc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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 9d 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.

.claude/agents/py-analyzer.md · 67 lines

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]
Changes

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.

  1. 9d ago First seen · 67 lines · 13 tokens per session scan A 70f4be1cb9bc

Subscribe to this mod's changes

py-analyzer is an agent published in the GitHub repository mylee04/who-ran-what (3 stars, last pushed 7mo ago), licensed MIT. It adds 13 tokens to every session and 295 once invoked, about $0.0001 per session on Opus 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.