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 skills/nicogenti/opencode-orchestrator-kit/python-conventionsnpx skills add NicoGenti/opencode-orchestrator-kit --skill python-conventionsgit clone --depth 1 https://github.com/NicoGenti/opencode-orchestrator-kitWhat 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.00032 | $0.00433 |
| Opus 5 | $0.00016 | $0.00217 |
| Sonnet 5 | $0.00006 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
python-conventions 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 2d 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.
What it actually says
Python Conventions
Based on PEP 8, the official Python style guide [web:74].
Naming
lower_case_with_underscoresfor functions and variables [web:87].CapitalizedWords(PascalCase) for classes [web:87].UPPERCASE_WITH_UNDERSCORESfor constants [web:87].- Always use
selfas the first argument of instance methods [web:84].
Formatting
- 4 spaces per indentation level; never mix tabs and spaces [web:74][web:84].
- Limit lines to 79 characters for code, 72 for docstrings/comments — relax this ceiling only if the project's linter config already does (e.g., Black's 88-char default) [web:74].
- Two blank lines around top-level functions and classes; one blank line between methods inside a class [web:74].
- One space around operators; no space immediately inside parentheses/brackets [web:87].
- Pick one quote style (single or double) and use it consistently across the codebase [web:87].
Imports
- Order: standard library, then third-party, then local application imports, each group separated by a blank line [web:87][web:84].
- Prefer one import per line; use explicit
from module import nameonly when it improves clarity.
Structure
- Use type hints on public function signatures.
- Use docstrings for modules, classes, and public functions describing purpose, not implementation.
- Keep functions focused; if a function mixes multiple responsibilities, split it.
When Reviewing
Flag mixed tabs/spaces, inconsistent quote style, and missing type hints on public APIs ahead of line-length nits if the project has its own formatter (Black/Ruff) already configured — defer to that tool's config over strict PEP 8 line length.
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.
- 2d ago First seen · 41 lines · 32 tokens per session scan A 42768a99ba81
python-conventions is a skill published in the GitHub repository NicoGenti/opencode-orchestrator-kit (5 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 433 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 skills, from other repositories
cao-workflow
Author and run CAO Python workflow scripts — multi-step, parameterized, fan-out orchestrations executed by cao workflow run. Use when the user wants a repeatable multi-step job (e.g. data analysis over many files, a review pipeline, a parameterized batch). Authoring ends at a validated script file; running it is a…
aidlc-portfolio
Coordinate multiple AI-DLC workflows across repositories and Git worktrees using an evidence-backed portfolio catalog and deterministic workspace tooling. Use when initializing an AI-DLC portfolio workspace, discovering organization or business context, registering projects and dependencies, creating child intents and…
cao-plugin
Create a new CAO (CLI Agent Orchestrator) plugin. Use this skill whenever the user wants to add a plugin that reacts to CAO lifecycle or messaging events, scaffold a plugin package, understand plugin requirements, or integrate an external system (Discord, Slack, dashboards, logging, metrics) with CAO. Also use when…
agui-author
Author live dashboard UI from an agent via the emitui MCP tool. Emit one of six allow-listed components (approvalcard, choiceprompt, diffsummary, progress, metric, agentcard) with JSON props and it renders in any AG-UI client watching the fleet. Use when you want the operator to see a decision, a diff, or a status…
cao-mcp-apps
Enable, operate, and extend CAO's MCP Apps surface — the host-rendered fleet dashboard visible inside MCP App hosts (Claude Desktop, ChatGPT, VS Code Copilot, Goose, Postman). Use when the user says "enable MCP Apps in CAO", "the ui://cao views aren't rendering", "rebuild MCP Apps bundles", "add a new ui://cao/ view"…
cao-provider
Create a new CLI agent provider for CAO (CLI Agent Orchestrator). Use this skill whenever the user wants to add support for a new CLI-based AI agent (e.g., a new coding assistant CLI), integrate a new provider, or scaffold a provider implementation. Also use when the user asks about the provider architecture, what…