Borrowing it
Nothing to install: this file belongs to jmstar85/oh-my-githubcopilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jmstar85/oh-my-githubcopilot/main/.github/skills/coding-standards/SKILL.mdgit clone --depth 1 https://github.com/jmstar85/oh-my-githubcopilotWrote 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/jmstar85/oh-my-githubcopilot/coding-standards)<a href="https://agentmods.dev/skills/jmstar85/oh-my-githubcopilot/coding-standards"><img src="https://agentmods.dev/badge/skills/jmstar85/oh-my-githubcopilot/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.
<a href="https://agentmods.dev/skills/jmstar85/oh-my-githubcopilot/coding-standards"><img src="https://agentmods.dev/badge/skills/jmstar85/oh-my-githubcopilot/coding-standards.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.00043 | $0.01369 |
| Opus 5.5 | $0.00017 | $0.00548 |
| Sonnet 5.5 | $0.00009 | $0.00274 |
| Haiku 4.5 | $0.00004 | $0.00137 |
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 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.
This is a copy
100% identical to coding-standards — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coding Standards
D9 Canonical Reference. This is the single source of truth for cross-language coding standards. Language-specific reviewers (
@typescript-reviewer,@python-reviewer, etc.) embed these rules. Agents cite this skill as "See also: /coding-standards."
Naming Conventions
Variables & Functions
| Language | Variables | Functions | Constants |
|---|---|---|---|
| TypeScript / JavaScript | camelCase |
camelCase |
SCREAMING_SNAKE_CASE |
| Python | snake_case |
snake_case |
SCREAMING_SNAKE_CASE |
| Go | camelCase |
camelCase |
CamelCase (exported) |
| Rust | snake_case |
snake_case |
SCREAMING_SNAKE_CASE |
| Java | camelCase |
camelCase |
SCREAMING_SNAKE_CASE |
| C# | camelCase |
PascalCase |
PascalCase |
| Swift | camelCase |
camelCase |
camelCase |
Classes / Types / Interfaces
PascalCase — all languages, no exceptions.
Booleans
Prefix with is, has, can, should: isLoading, hasError, canEdit, shouldRefresh.
Collections
Plural nouns: users, errors, items — not userList, errorArray.
Avoid
- Single-letter variables outside loop counters (
i,j,kare OK in loops) - Abbreviations that save under 3 characters:
usr→user,mgr→manager - Redundant type names:
UserInterface,UserClass,UserObject→ justUser
Function Design
- Max length: 50 lines (firm guideline; > 80 lines is always a split target)
- Single responsibility: one function, one job — if "and" appears in the description, split it
- Max parameters: 3; beyond that, use an options/config object
- Cyclomatic complexity: ≤ 10; > 15 is a mandatory refactor target
- Nesting depth: ≤ 3 levels; use early returns to flatten
Early Return Pattern (preferred)
// BEFORE — deep nesting
function handle(input) {
if (input) {
if (input.valid) {
return process(input);
}
}
return null;
}
// AFTER — early returns
function handle(input) {
if (!input || !input.valid) return null;
return process(input);
}
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 · 145 lines · 43 tokens per session scan A 669714e3c002
coding-standards is a skill published in the GitHub repository jmstar85/oh-my-githubcopilot (160 stars, last pushed 5mo ago), licensed MIT. It adds 43 tokens to every session and 1,369 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to coding-standards, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…