agentmods.dev

coding-standards

coding-standards is a skill for Claude Code, Codex from ithinkihaveacat/dotfiles. It costs 81 tokens per session (1,113 once invoked), scanned A, original, Apache-2.0.

A repository guide for coding style, formatting, linting, command-line design, HTTP caching, and Git commit conventions. Linters check code for likely problems, while formatters apply consistent layout.

In plain words
What is it for?
Use it when writing, reviewing, formatting, or checking code, and when preparing conventional commit messages or synchronizing generated command help.
Why use it?
It keeps changes consistent with the repository and catches style or quality issues before review. The included scripts cover Python, shell, Markdown, Kotlin, JSON, and XML.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 48repo changed 15d ago A scan SkillSpector: pass 81 tokens original Apache-2.0

Good fit Use it when writing, reviewing, formatting, or checking code, and when preparing conventional commit messages or synchronizing generated command help.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ithinkihaveacat/dotfiles/coding-standards
View source ↗ ithinkihaveacat/dotfiles
Install

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.

Any agent
npx skills add ithinkihaveacat/dotfiles --skill coding-standards
Clone the repo
git clone --depth 1 https://github.com/ithinkihaveacat/dotfiles

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for coding-standards

README.md
[![agentmods](https://agentmods.dev/badge/skills/ithinkihaveacat/dotfiles/coding-standards/github.svg)](https://agentmods.dev/skills/ithinkihaveacat/dotfiles/coding-standards)
Your own site
<a href="https://agentmods.dev/skills/ithinkihaveacat/dotfiles/coding-standards"><img src="https://agentmods.dev/badge/skills/ithinkihaveacat/dotfiles/coding-standards/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.

agentmods 80×15 button for coding-standards

Your own site · 80×15
<a href="https://agentmods.dev/skills/ithinkihaveacat/dotfiles/coding-standards"><img src="https://agentmods.dev/badge/skills/ithinkihaveacat/dotfiles/coding-standards.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 81 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,113 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00081 $0.01113
Opus 5.5 $0.00032 $0.00445
Sonnet 5.5 $0.00016 $0.00223
Haiku 4.5 $0.00008 $0.00111

Measured 15d ago against content hash d379ce67bf90, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 15d 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.

skills/coding-standards/SKILL.md · 110 lines

How it starts

The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Coding Standards

This skill provides coding guidelines, linters, and formatters for making changes across languages and domains in this repository.

Formatting Scripts

Helper scripts in scripts/ encapsulate repository-wide style rules and lint checks. References to scripts/... are relative to this skill directory. All scripts support formatting multiple files in place, or reading from stdin and writing to stdout when no arguments are provided.

  • scripts/python-format: Format and lint Python files using ruff (supports --check and recursive directory scanning).
  • scripts/shell-format: Format and lint shell scripts (POSIX/Bash) using shfmt and shellcheck (supports --check and recursive directory scanning; Fish scripts use fish_indent).
  • scripts/markdown-format: Format Markdown files using mdformat with GFM and frontmatter preservation (supports --check for drift detection).
  • scripts/command-index-format: Refresh generated --help blocks in command-index.md files (marker comments; supports --check and --all).
  • scripts/kotlin-format: Format Kotlin files using ktfmt with kotlinlang style.
  • scripts/json-format: Format JSON files using jq.
  • scripts/xml-format: Format XML files using xmllint.

Always prefer the helper scripts in scripts/ over raw tool invocations to guarantee consistent repository formatting rules.

Core Standards & Guidelines

Markdown Quality

All Markdown files must be formatted and linted with scripts/markdown-format. Headings must use clean, unadorned ATX styles (## Heading) without numbers, manual bolding, or ALL CAPS. See references/markdown.md.

Python Development

All Python files must be linted and formatted with scripts/python-format. Follow type annotation conventions, structured CLI argument parsing with argparse, and error handling standards. See references/python.md.

Read the full file on GitHub · 110 lines

Files

What ships with it

24 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 15d ago Changed · -8 lines d379ce67bf90
  2. 17d ago Changed · +2 lines 2f85842e36ba
  3. 1mo ago Changed c56310941b3f
  4. 1mo ago Changed fd467fd41be9
  5. 1mo ago First seen · 116 lines · 81 tokens per session scan A f903a0024610

Subscribe to this mod's changes

coding-standards is a skill published in the GitHub repository ithinkihaveacat/dotfiles (48 stars, last pushed yesterday), licensed Apache-2.0. It adds 81 tokens to every session and 1,113 once invoked, about $0.0003 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-30.

CommitsGit and workflowWriting and docsdotfilesfishshell
Related

Other skills, from other repositories

smart-commit

Analyzes all uncommitted changes (staged and unstaged), groups them into atomic commits by logical purpose, and generates clear conventional commit messages with practical, context-rich bodies. Use when the user asks to "smart commit", "group my commits", "split into atomic commits", "organize my changes into…

wunki/dotfiles · 134 tokens

global-commit

Create a git commit following Conventional Commits specification.

rgomezcasas/dotfiles · 13 tokens

git-commit

This skill should be used BEFORE running any git commit command. Triggers when about to run git commit. Ensures commit messages follow Conventional Commits specification.

fredrikaverpil/dotfiles · 36 tokens

mbo-plan

Plan a new objective end-to-end in this repo's docs/mbo Management-By-Objective system — turn a GitHub issue or a gss draft-PR worktree into consistent design/spec/plan artifacts and track it in docs/mbo/index.md. Use this whenever the user wants to START planning or designing a new feature, skill, CLI, or service…

sfc-gh-eraigosa/dotfiles · 260 tokens

herdr

Use when the user mentions herdr or is working inside a herdr pane and wants to save/restore a pane layout, change herdr's theme, prefix or other preferences on this host only, start or check on an agent in another herdr pane, add, turn off or open a herdr plugin (file viewer, keybindings), or asks why the herdr…

sfc-gh-eraigosa/dotfiles · 91 tokens

wispr-flow-debug

Debug and test the Wispr Flow AutoHotkey dictation triggers (Copilot key + extra keys) from WSL by deploying macos.ahk to the Windows Desktop, reloading AutoHotkey, and reading the debug log. Use when an activation/trigger key isn't starting/stopping dictation, when the overlay clicks land wrong, or when verifying a…

sfc-gh-eraigosa/dotfiles · 87 tokens