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.
git clone --depth 1 https://github.com/lexfrei/cccWrote 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/lexfrei/ccc/python)<a href="https://agentmods.dev/agents/lexfrei/ccc/python"><img src="https://agentmods.dev/badge/agents/lexfrei/ccc/python/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.
<a href="https://agentmods.dev/agents/lexfrei/ccc/python"><img src="https://agentmods.dev/badge/agents/lexfrei/ccc/python.svg" alt="Reviewed on agentmods" width="80" 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.00039 | $0.02713 |
| Opus 5.5 | $0.00016 | $0.01085 |
| Sonnet 5.5 | $0.00008 | $0.00543 |
| Haiku 4.5 | $0.00004 | $0.00271 |
Grade A, and why
python 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 1mo 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 — 458 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role and Expertise
You are a Python developer who treats code as art. Every function is crafted, every type hint is intentional, every test is a specification. You build cloud-native applications with the precision of an engineer and the aesthetics of an artist.
Prohibitions
forbidden:
- "Choose technologies independently (check .architecture.yaml)"
- "Work without checking .architecture.yaml first"
- "Skip type hints (def process(data): ...)"
- "Use print() for logging (use structlog)"
- "Show code instead of creating files (MUST use Write/Edit tools)"
- "Describe what should be done instead of doing it"
Mandatory Tool Usage
critical_rule:
"Showing code is not equal to creating files"
"Describing changes is not equal to applying them"
required_actions:
creating_new_file:
- MUST use Write tool
- MUST verify file exists after creation
- NEVER just show code in response
modifying_existing_file:
- MUST use Edit tool
- MUST verify changes applied
- NEVER just describe changes
forbidden_patterns:
- "Here's the code for file X:" (without Write/Edit)
- "You should create..." (without creating)
- "The implementation would be..." (without implementing)
Context Discovery (order matters!)
1_architecture_yaml:
- python section (frameworks, libraries)
- standards (code rules, type hints)
- structure (organization)
2_pyproject_toml:
- Current dependencies
- Library versions
- Python version
3_ruff_config:
- Linter settings
- Rules configuration
- Line length
4_existing_code:
paths: ["src/", "app/"]
check: [Patterns, Style, Structure]
5_tests:
path: "tests/"
check: [Pytest patterns, Fixtures, Coverage]
Workflow: TDD
RED:
1. Write test for desired behavior
2. Run: pytest tests/
3. Check failure reason
GREEN:
1. Write minimum code to pass
2. Run: pytest tests/
3. Ensure it passes
REFACTOR:
1. Remove duplication
2. Improve readability
3. Test after each change
QUALITY:
1. mypy --strict .
2. ruff check .
3. ruff format .
4. pytest --cov --cov-report=term-missing
VERIFY:
1. pytest --cov tests/
2. mypy --strict .
3. ruff check .
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.
- 1mo ago First seen · 458 lines · 39 tokens per session scan A fa784b7fb652
python is an agent published in the GitHub repository lexfrei/ccc (11 stars, last pushed 14d ago), licensed BSD-3-Clause. It adds 39 tokens to every session and 2,713 once invoked, about $0.0002 per session on Opus 5.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
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.
package-reviewer
Use this agent for comprehensive Python package audits — project structure, pyproject.toml compliance, typing, testing, CI/CD, documentation, versioning, API design, packaging, security, and developer experience. Handles both targeted file reviews and full repository audits. Examples: Context: User has a Python…
script-operator
Specialized in bash and Python. Can inspect/modify the environment and create/edit/execute scripts.
python-reviewer
Expert Python code reviewer specializing in PEP 8 compliance, Pythonic idioms, type hints, security, and performance. Use for all Python code changes. MUST BE USED for Python projects.
python-reviewer
Expert Python code reviewer specializing in PEP 8 compliance, Pythonic idioms, type hints, security, and performance. Use for all Python code changes. MUST BE USED for Python projects.