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 commands/mathisk2095/jko-claude-plugins/py-critiquegit clone --depth 1 https://github.com/mathisk2095/jko-claude-pluginsWrote 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/commands/mathisk2095/jko-claude-plugins/py-critique)<a href="https://agentmods.dev/commands/mathisk2095/jko-claude-plugins/py-critique"><img src="https://agentmods.dev/badge/commands/mathisk2095/jko-claude-plugins/py-critique.svg" alt="Measured on agentmods" 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.00029 | $0.00717 |
| Opus 5 | $0.00015 | $0.00358 |
| Sonnet 5 | $0.00006 | $0.00143 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
py-critique 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conduct a comprehensive architecture critique of the Python backend code. If $ARGUMENTS is provided, focus on that module, file, or feature area. Otherwise critique the entire backend.
First: Use the python-backend-expert skill for all design principles, patterns, and anti-patterns.
Critique Process
-
Detect framework: Litestar (Controllers, Provide) or FastAPI (routers, Depends). Adapt terminology.
-
Map the architecture:
- Read the composition root (app.py, main.py, or container.py) to understand DI wiring
- Identify the layer structure: entrypoints / application / domain / infrastructure
- Trace the dependency graph: what imports what?
-
AI Slop Detection (start here): Run the detection checklist from
references/ai-slop.md. Check for AS-01 through AS-12. -
Review each layer using the python-backend-expert skill's review checklist (all 13 points).
-
Check file sizes: Flag any module >300 lines as a candidate for splitting. Flag >500 as urgent.
-
Anti-pattern scan: Check for AP-01 through AP-22 from
references/anti-patterns.md.
Output Format
AI Slop Verdict
Start here. Pass/fail: Does this code look AI-generated? Run the detection checklist. Be brutally honest. List specific tells with file and line. If 3+ tells are found, the code needs architectural review.
Architecture Map
Brief overview of detected architecture (layers, DI approach, framework).
What's Working Well
Highlight 2-4 patterns done correctly. Reinforce good architecture.
Priority Issues
Top 5-8 issues, ordered by severity (blocking > important > nit):
For each:
- What: Name the problem with anti-pattern ID (AP-xx or AS-xx)
- Where: File path and line
- Why it matters: Concrete consequence
- Fix: Specific code change or restructuring needed
- Command: Which command to use (
/py-harden,/py-structure)
File Size Report
List any files >300 lines with line count and suggested split strategy.
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.
- 5d ago First seen · 78 lines · 29 tokens per session scan A 969198df4407
py-critique is a command published in the GitHub repository mathisk2095/jko-claude-plugins (3 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 717 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.
Other commands, from other repositories
route
Generate a Kibana server route with proper validation, error handling, and TypeScript types. Supports all HTTP methods and common patterns like CRUD operations and Elasticsearch queries.
embeddable
Generate a custom Embeddable panel that can be placed on Kibana Dashboards, with factory registration, input/output types, and React rendering.
expression
Generate custom Expression Functions and Renderers for use in Kibana Canvas, Lens, and Dashboard visualizations.
fast-dev
Set up a fast development environment for Kibana plugin development — mock server, optimized config, test infrastructure, and Storybook setup to minimize Kibana restarts.
saved-object
Generate a custom Saved Object type with registration, mappings, migrations, CRUD service, and management integration for a Kibana plugin.
ui-action
Generate custom UI Actions and Triggers for inter-plugin communication in Kibana — register actions, attach to triggers, execute across plugins.