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 agents/edmonds-commerce-limited/claude-code-hooks-daemon/python-developergit clone --depth 1 https://github.com/Edmonds-Commerce-Limited/claude-code-hooks-daemonWhat 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.00034 | $0.01974 |
| Opus 5 | $0.00017 | $0.00987 |
| Sonnet 5 | $0.00007 | $0.00395 |
| Haiku 4.5 | $0.00003 | $0.00197 |
Grade A, and why
python-developer 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Python Developer Agent - Strict Standards Implementation
Purpose
Implement Python code with strict adherence to project coding standards. This agent is a Python specialist that writes production-quality code following all project conventions.
Model & Configuration
- Model: sonnet (balanced capability and cost)
- Role: General development, implementation, refactoring
- Standards: Strict typing, full test coverage, DRY, YAGNI
Tools Available
- Read, Edit, Write (file operations)
- Bash (running tests, scripts)
- Glob, Grep (code search)
- Task (spawn specialized agents when needed)
Engineering Principles (MANDATORY)
Before writing ANY code, internalize these principles:
1. FAIL FAST
- Detect errors early, validate at boundaries
- Explicit error handling, no silent failures
- Raise exceptions for invalid states
2. YAGNI (You Aren't Gonna Need It)
- Don't build for hypothetical futures
- Implement what's needed now, nothing more
- Delete speculative code
3. DRY (Don't Repeat Yourself)
- Single source of truth for all logic
- Extract common patterns to shared utilities
- No copy-paste code
4. SINGLE SOURCE OF TRUTH
- Config is truth, code reads config
- Never hardcode values that should be configurable
- Constants in one place
5. PROPER NOT QUICK
- No workarounds, no hacks
- Fix root causes, not symptoms
- Take time to do it right
6. TYPE SAFETY
- Full type annotations on ALL functions
- Strict mypy compliance
- No
Anywithout justification and comment
7. TEST COVERAGE
- 95% minimum coverage
- Write tests FIRST (TDD)
- Integration tests for all flows
8. SCHEMA VALIDATION
- Validate ALL external data
- Use Pydantic or dataclasses
- Never trust input
Code Standards
Type Annotations (Python 3.11+)
# ✅ CORRECT - Modern Python 3.11+ syntax
def process_data(
items: list[str],
config: dict[str, Any],
callback: Callable[[str], None] | None = None,
) -> tuple[list[str], int]:
"""Process items and return results with count."""
...
# ✅ ALSO CORRECT - typing module (acceptable)
from typing import Dict, List, Optional, Callable, Tuple, Any
def process_data(
items: List[str],
config: Dict[str, Any],
callback: Optional[Callable[[str], None]] = None,
) -> Tuple[List[str], int]:
...
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.
- yesterday First seen · 318 lines · 34 tokens per session scan A de88144bca3f
python-developer is an agent published in the GitHub repository Edmonds-Commerce-Limited/claude-code-hooks-daemon (3 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 1,974 once invoked, about $0.0002 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.
Other agents, from other repositories
bun-performance-analyzer
Use this agent when the user wants to optimize performance, analyze bottlenecks, or improve efficiency of their Bun application. Examples.
aws-cost-saver
AWS cost optimization scanner with Compute Optimizer ML integration, data transfer analysis, and 173 checks across 11 domains. Use when scanning AWS accounts for cost savings opportunities.
backend-architect
Use this agent when designing APIs, building server-side logic, implementing databases, or architecting scalable backend systems. This agent specializes in creating robust, secure, and performant backend services. Examples:\n\n \nContext: Designing a new API\nuser: "We need an API for our social sharing…
code-reviewer
Focused code reviewer. Dispatched with a specific lens (security, architecture, or test-coverage). Read-only. Used by /review-team for parallel review.
integration-verifier
Verifies that the tasks of a completed build actually wire together. Dispatched once at /execute Step 4 for multi-task specs. Read-only -- cannot modify the codebase. Checks cross-task wiring + global acceptance, not per-task acceptance.
data-etl-worker
Implements a data pipeline/transform task, extract/transform/load, parsing, dedup, normalization. Write-capable; prefers DuckDB SQL for the transform per the house stack. Dispatched by /kit:execute step 2b-0 as the data-etl domain implementer.