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/sponge-b0b/polaris/coding-standardsnpx skills add sponge-b0b/Polaris --skill coding-standardsgit clone --depth 1 https://github.com/sponge-b0b/PolarisWrote 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/skills/sponge-b0b/polaris/coding-standards)<a href="https://agentmods.dev/skills/sponge-b0b/polaris/coding-standards"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/coding-standards.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 | $0.00081 | $0.03164 |
| Opus 5 | $0.00041 | $0.01582 |
| Sonnet 5 | $0.00016 | $0.00633 |
| Haiku 4.5 | $0.00008 | $0.00316 |
Grade A, and why
coding-standards 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 4d 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 — 481 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coding Standards
Apply these standards whenever creating, modifying, refactoring, fixing, or reviewing Python source code.
Optimize for correct, readable, maintainable Python with the minimum total complexity necessary.
Scope and Precedence
These rules apply to Python source and tests.
Before changing code:
- Read applicable repository instructions such as
AGENTS.md. - Inspect relevant code, callers, tests, and established patterns.
- Inspect repository configuration such as
pyproject.toml,ruff.toml, andmypy.ini. - Follow repository-configured Python, Ruff, Mypy, formatting, and testing rules over generic defaults in this skill.
- Follow authoritative ADRs and
docs/current/sources when a coding rule depends on project architecture or semantics.
Do not modify lint, formatting, typing, or test configuration merely to make code pass unless changing that policy is itself part of the task.
A direct user requirement or documented repository rule overrides a design preference here. Required correctness, security, data integrity, domain contracts, scoring semantics, and observability are not optional simplifications.
Polaris Non-Negotiables
Data-Contract Boundaries
When changing application-service, intelligence, runtime, persistence, or other data-contract boundaries, read:
docs/current/domain-contracts-data-semantics-contract-semantics.md
Follow its canonical classification and boundary rules.
In particular:
- exchange stable internal semantics through typed objects;
- use mappings only at approved serialization, vendor, telemetry, persistence, report, artifact, runtime, or transport boundaries;
- do not hide stable business dimensions in generic metadata or undifferentiated mappings;
- promote stabilized semantics from extension mappings into explicit typed fields;
- distinguish fallback or unavailable values from canonical observations.
For AI-adjacent outputs, preserve the applicable RiskAuthorityContract requirements defined by the same authoritative source.
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.
- 4d ago First seen · 481 lines · 81 tokens per session scan A 25e824675a17
coding-standards is a skill published in the GitHub repository sponge-b0b/Polaris (4 stars, last pushed today), licensed Apache-2.0. It adds 81 tokens to every session and 3,164 once invoked, about $0.0004 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
python-best-practices
Python coding best practices. Use when writing or reviewing Python code. Covers type hints, error handling, and common patterns.
python-lib-analyzer
Analyze any Python library structure, explore modules, classes, and functions with signatures and documentation.
nornweave-api
Give AI agents their own email inboxes using the NornWeave API. Use when building email agents, sending/receiving emails programmatically, managing inboxes, retrieving threads, searching messages, or integrating with email providers (Mailgun, SES, SendGrid, Resend). NornWeave provides LLM-ready markdown parsing and…
commit-push
Commit and push the changes made on this chat session to the current branch. Use best practices from Conventional Commits.
commit
Commit the changes made on this chat session to the current branch. Use best practices from Conventional Commits.
http-client-migration
Flawed HTTP client migration procedure requiring patch.