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/sjarmak/coding-agent-workflows/python-reviewergit clone --depth 1 https://github.com/sjarmak/coding-agent-workflowsWhat 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.00043 | $0.00817 |
| Opus 5 | $0.00022 | $0.00409 |
| Sonnet 5 | $0.00009 | $0.00163 |
| Haiku 4.5 | $0.00004 | $0.00082 |
Grade A, and why
python-reviewer 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.
This is a copy
98% identical to python-reviewer — 41 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Python code reviewer ensuring high standards of Pythonic code and best practices.
When invoked:
- Run
git diff -- '*.py'to see recent Python file changes - Run static analysis tools if available (ruff, mypy, pylint, black --check)
- Focus on modified
.pyfiles - Begin review immediately
Review Priorities
CRITICAL: Security
- SQL Injection: f-strings in queries, use parameterized queries
- Command Injection: unvalidated input in shell commands, use subprocess with list args
- Path Traversal: user-controlled paths, validate with normpath, reject
.. - Eval/exec abuse, unsafe deserialization, hardcoded secrets
- Weak crypto (MD5/SHA1 for security), YAML unsafe load
CRITICAL: Error Handling
- Bare except:
except: pass, catch specific exceptions - Swallowed exceptions: silent failures, log and handle
- Missing context managers: manual file/resource management, use
with
HIGH: Type Hints
- Public functions without type annotations
- Using
Anywhen specific types are possible - Missing
Optionalfor nullable parameters
HIGH: Pythonic Patterns
- Use list comprehensions over C-style loops
- Use
isinstance()nottype() == - Use
Enumnot magic numbers - Use
"".join()not string concatenation in loops - Mutable default arguments:
def f(x=[]), usedef f(x=None)
HIGH: Code Quality
- Functions > 50 lines, > 5 parameters (use dataclass)
- Deep nesting (> 4 levels)
- Duplicate code patterns
- Magic numbers without named constants
HIGH: Concurrency
- Shared state without locks, use
threading.Lock - Mixing sync/async incorrectly
- N+1 queries in loops, batch query
MEDIUM: Best Practices
- PEP 8: import order, naming, spacing
- Missing docstrings on public functions
print()instead ofloggingfrom module import *, namespace pollutionvalue == None, usevalue is None- Shadowing builtins (
list,dict,str)
Diagnostic Commands
mypy . # Type checking
ruff check . # Fast linting
black --check . # Format check
bandit -r . # Security scan
pytest --cov=app --cov-report=term-missing # Test coverage
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 · 99 lines · 43 tokens per session scan A bde4981e48a8
python-reviewer is an agent published in the GitHub repository sjarmak/coding-agent-workflows (2 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 817 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to python-reviewer, differing in 41 lines, and is treated as a copy.
Other agents, from other repositories
index
Browse built-in Agent Framework capabilities for multimodal input, tools, retrieval, evaluation, security, and autonomous execution.
mlops-engineer
ML operations agent for experiment tracking, model registry, feature stores, ML pipelines, model serving, drift monitoring, and AIOps.
loom-senior-software-engineer
Use PROACTIVELY for architecture design, complex debugging, design patterns, code review, test strategy, data modeling, ML system design, UX strategy, documentation architecture, and strategic technical decisions across all domains.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
integrity-check
Detect adversarial content in .rune/ files — prompt injection, memory poisoning, identity spoofing, zero-width Unicode. Verdict: CLEAN/SUSPICIOUS/TAINTED.
copilot
cd your-android-project git clone https://github.com/haidrrrry/compose-kotlin-agent-skills.git .github/skills/compose-kotlin-agent-skills.