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/railtownai/railtracks/code-stylenpx skills add RailtownAI/railtracks --skill code-stylegit clone --depth 1 https://github.com/RailtownAI/railtracksWrote 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/railtownai/railtracks/code-style)<a href="https://agentmods.dev/skills/railtownai/railtracks/code-style"><img src="https://agentmods.dev/badge/skills/railtownai/railtracks/code-style.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.00056 | $0.00615 |
| Opus 5 | $0.00028 | $0.00308 |
| Sonnet 5 | $0.00011 | $0.00123 |
| Haiku 4.5 | $0.00006 | $0.00061 |
Grade A, and why
code-style 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
Code style
Before finishing any code change in this repo, check the diff against these rules. Each one comes from a recurring, repeated PR review comment on railtracks, not a hypothetical style preference.
- Lint/format: run
ruff check --fixandruff format, required for every PR (CI-enforced), so treat a change as unfinished until both are clean. - Imports: prefer top-level imports. Local/inline imports are fine when there's a real reason (e.g.
deferring an expensive or optional dependency like
litellm); don't add them out of habit, and don't let a lint failure be the excuse either way. - Tests: new functionality gets tests in the matching package's
tests/directory; don't leave a behavior change uncovered. - Docstrings: must match the actual signature (param names, types,
| None/Iterable[...]etc.). Update the docstring any time a signature changes. - Tool docstrings/type hints: for any
@rt.function_node-wrapped tool, the docstring is the literal tool description the LLM sees and the type hints define its JSON schema parameters; don't write vague docstrings or omit type hints on a tool function. - Module-level comment strings: a docstring at the top of a file is welcome. Avoid long inline paragraph-style comments in the body of the code; keep inline comments short and targeted.
- Typing: no bare
Anywhen a concrete type is available or already imported nearby. Don't reach forAnyas a quick fix to silence something that's actually broken, either; fix the real type mismatch. - TODOs: no inline
# TODOcomments. Either fix it now or file a tracked GitHub issue and reference it. - Cruft: no dead/commented-out code, no stray debug/scratch files left in a change.
- Mutable defaults: don't store a mutable default (
x or []) by reference and mutate it later; copy defensively. - Errors: use
repr(e)rather thanstr(e)in error/log messages. __init__.py: don't add docstrings to__init__.pyfiles; not this repo's convention.- Consistency with siblings: when adding a new variant of something that already has 2+ siblings (chunkers, loaders, LLM providers, etc.), match their existing shape/behavior rather than introducing an ad hoc one-off.
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 · 39 lines · 56 tokens per session scan A 789e59deec68
code-style is a skill published in the GitHub repository RailtownAI/railtracks (148 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 615 once invoked, about $0.0003 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-03.
Other skills, from other repositories
testing-python
Write and evaluate effective Python tests using pytest. Use when writing tests, reviewing test code, debugging test failures, or improving test coverage. Covers test design, fixtures, parameterization, mocking, and async testing.
migrating-langchain-to-pydantic-ai
Migrate Python LangChain or LangGraph applications to Pydantic AI. Use for LangChain agents, chains, LCEL, or direct LangGraph graphs, persistence, interrupts, and streaming. Do not use for migrations centered on createdeepagent or Deep Agents harness features.
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
python-code-reviewer
Review Python OpenInference instrumentation code for correctness and completeness. Use this skill when reviewing a Python instrumentor package — whether it's a new instrumentor, a PR that modifies one, or when the user asks to audit/review/check an existing instrumentor's code quality. Trigger on phrases like "review…
build-cli
Build and install the Python CLI (planoai). Use after making changes to cli/ code to install locally.
test-generator
Generate pytest test cases for Python functions and classes.