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 skills add nxtg-ai/forge-plugin --skill coding-standardsgit clone --depth 1 https://github.com/nxtg-ai/forge-pluginWrote 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/nxtg-ai/forge-plugin/coding-standards)<a href="https://agentmods.dev/skills/nxtg-ai/forge-plugin/coding-standards"><img src="https://agentmods.dev/badge/skills/nxtg-ai/forge-plugin/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/nxtg-ai/forge-plugin/coding-standards"><img src="https://agentmods.dev/badge/skills/nxtg-ai/forge-plugin/coding-standards.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00108 | $0.03989 |
| Opus 5 | $0.00054 | $0.01995 |
| Sonnet 5 | $0.00022 | $0.00798 |
| Haiku 4.5 | $0.00011 | $0.00399 |
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 7d 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 — 368 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coding Standards
A language-agnostic baseline for consistent, readable, secure code. This skill ships inside a plugin you install in your own project — Python, TypeScript/JavaScript, Rust, Go, or anything else. Apply the principles universally; use the language section that matches the file at hand. The numeric thresholds here are recommended defaults — tune them to your project and enforce them with your own linter/CI, not from memory.
Core Principles (Universal)
- Readability counts — code is read far more often than written.
- Explicit over implicit — clear intent beats clever tricks.
- Simple over complex — favor the straightforward solution.
- Consistency matters — follow the existing patterns in the codebase you're in.
- Single responsibility — one module/class/function does one thing well.
Naming Conventions (by language)
| Element | Python | TypeScript/JS | Rust | Go |
|---|---|---|---|---|
| Files/modules | snake_case.py |
kebab-case.ts / camelCase.ts |
snake_case.rs |
snake_case.go |
| Types/Classes | PascalCase |
PascalCase |
PascalCase |
PascalCase |
| Functions | snake_case |
camelCase |
snake_case |
camelCase (unexported) / PascalCase (exported) |
| Variables | snake_case |
camelCase |
snake_case |
camelCase |
| Constants | SCREAMING_SNAKE_CASE |
SCREAMING_SNAKE_CASE |
SCREAMING_SNAKE_CASE |
PascalCase / camelCase |
| Private/internal | _leading_underscore |
#private field / _prefix |
module-private (no pub) |
lowercase first letter |
Universal rules:
- No intent-obscuring abbreviations:
tp→template_path,genProj→generate_project,usrRepo→user_repository. - Boolean names read as predicates:
is_valid,has_access,can_retry. - In Go, exported vs unexported is the capitalization of the first letter — this is the language's access control, not a convention you can opt out of.
- Don't fight the ecosystem:
camelCasein Python orsnake_casein TS/JS reads as a mistake to every reviewer.
What ships with it
3 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.
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.
- 7d ago First seen · 368 lines · 108 tokens per session scan A eeb770e33e14
Coding Standards is a skill published in the GitHub repository nxtg-ai/forge-plugin (5 stars, last pushed today), licensed MIT. It adds 108 tokens to every session and 3,989 once invoked, about $0.0005 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
github-commenting
How to post clean, rich, deduplicated GitHub PR review comments — suggestion blocks, multi-line anchors, markers, formatting rules. Load before posting or fixing any PR comment.
ticketreview-commit
Thorough code review, verify requirements met, commit with detailed message.
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.