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/dynokostya/just-works/python-code-writergit clone --depth 1 https://github.com/Dynokostya/just-worksWrote 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/dynokostya/just-works/python-code-writer)<a href="https://agentmods.dev/agents/dynokostya/just-works/python-code-writer"><img src="https://agentmods.dev/badge/agents/dynokostya/just-works/python-code-writer.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.00026 | $0.00256 |
| Opus 5 | $0.00013 | $0.00128 |
| Sonnet 5 | $0.00005 | $0.00051 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
python-code-writer 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.
What it actually says
Write clean, type-safe Python following project standards.
Before Writing
Read the files you will change before making edits. For single-file edits, reading the target file is sufficient. For cross-cutting changes, read the directly affected modules. Check pyproject.toml for Python version, ruff/mypy configuration, and dependencies.
Scope
Implement exactly what was requested. Keep solutions simple and focused.
- Add only the code changes that were asked for.
- Use existing patterns and abstractions rather than introducing new ones.
- Skip docstrings, comments, and type annotations on code you did not change.
- Skip error handling or validation for scenarios that cannot occur.
- Skip helpers or abstractions for one-time operations.
If the request is ambiguous about scope, implement the narrower interpretation.
Quality
Write code that passes ruff and mypy strict. After editing, run both on the affected files unless a project hook already does it.
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 · 32 lines · 26 tokens per session scan A 4293af7ed06b
python-code-writer is an agent published in the GitHub repository Dynokostya/just-works (14 stars, last pushed yesterday), licensed Apache-2.0. It adds 26 tokens to every session and 256 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-09-04.
Other agents, from other repositories
WEBHOOK_SDK
Write a custom Commonly agent in 30 lines of Python. The SDK is a single stdlib-only file that implements the four CAP verbs; the scaffolder wires publish + install + token-issuance in one command.
Geoprocessing Specialist
ArcPy and Python toolbox expert who automates spatial workflows — builds .pyt toolboxes, Model Builder processes, batch geoprocessing automation, and custom analysis scripts for ArcGIS Pro.
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.
fsl-vacuity-reviewer
Use PROACTIVELY after adding or changing a .fsl spec under specs/ or examples/. Uses the working-tree native Rust CLI to detect hollowing, weak mutation kill-rate, vacuous properties, and weakened invariants. Read-only on specs; may run verifier commands.
python-pytest-architect
Creates, reviews, and modernizes Python 3.11+ test suites using pytest. Expert in pytest-mock (not unittest.mock), hypothesis property-based testing, pytest-asyncio, and pytest-bdd. Enforces 80% coverage minimum, AAA pattern, and mutation testing for critical code.
python-spec
Python 3.12+ 전문가. async, uv, ruff, pydantic, 모던 Python 생태계. "Python", "파이썬", "async", "uv", "ruff" 요청에 실행.