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/jeonje/claude-plugins/coding-conventionsnpx skills add JeonJe/claude-plugins --skill coding-conventionsgit clone --depth 1 https://github.com/JeonJe/claude-pluginsWhat 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.00088 | $0.00868 |
| Opus 5 | $0.00044 | $0.00434 |
| Sonnet 5 | $0.00018 | $0.00174 |
| Haiku 4.5 | $0.00009 | $0.00087 |
Grade A, and why
coding-conventions 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 2d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coding Conventions
Rules distilled from recurring review findings and production incidents. Each rule carries a one-line WHY; heavier rules keep their mechanics and precedents in references/.
How to apply
- Before writing code, read the target module's existing patterns first — new code mirrors the module's standard pattern (rule §4).
- While writing or reviewing, check the core rules below.
- When a rule's short form isn't enough to judge, read its detail file in
references/before making a verdict.
Core rules (short form)
| § | Rule | Detail |
|---|---|---|
| 1 | No external metadata (ticket IDs, spec section numbers, volatile magic values) in code comments/names | references/conventions-core.md |
| 2 | No meta-words (Value, Helper, Util, Manager) in names — use domain nouns/intent verbs |
same |
| 3 | No comments restating obvious code — comments are for non-obvious WHY only | same |
| 4 | New code mirrors the module's existing pattern | same |
| 5 | Explicit git add — never -A/. |
same |
| 7 | Paired algorithmic constants: changing one requires re-verifying the other | same |
| 13 | Reuse existing infra/harness; existence is not effectiveness — prove it fires | references/s13-existing-infra-reuse.md |
| 14 | Re-verify inherited claims against HEAD before propagating | references/s14-inherited-claims.md |
| 16 | finally/catch side work must never mask the main flow's result | references/s16-finally-masking.md |
| 17 | Infra clients: boot-time synchronous connect and conditional bean consumption are deliberate contracts | references/s17-infra-client-boot.md |
| 19 | Strong negative verdicts ("impossible / converges to zero") need one runtime observation first | references/s19-runtime-observation.md |
| 22 | rg -r is --replace, not recursive — verify exact literals with grep -n or Read |
references/conventions-core.md |
| 23 | New dependencies pass a review gate (stdlib first, maintenance, duplicate-role check) | references/conventions-core.md |
What ships with it
11 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.
- references/coding-conventions-java.md 1.9 KB
- references/conventions-core.md 11 KB
- references/core-principles.md 2.8 KB
- references/domain-model-guidelines.md 4.8 KB
- references/patterns.md 1.1 KB
- references/readable-code.md 4.8 KB
- references/s13-existing-infra-reuse.md 2.9 KB
- references/s14-inherited-claims.md 1.5 KB
- references/s16-finally-masking.md 1.1 KB
- references/s17-infra-client-boot.md 1.5 KB
- references/s19-runtime-observation.md 2.6 KB
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.
- 2d ago First seen · 49 lines · 88 tokens per session scan A 918b158d551a
coding-conventions is a skill published in the GitHub repository JeonJe/claude-plugins (3 stars, last pushed 28d ago), licensed MIT. It adds 88 tokens to every session and 868 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
api-testing
HTTP API testing with Supertest (TS) and httpx/pytest (Python). Use when the user mentions API testing, Supertest, httpx, REST/GraphQL validation, or HTTP response errors.
phpunit-test-team-reviewing
Use this skill when the user asks for a team-based, consensus, multi-reviewer, or red-team review of Shopware PHPUnit tests — trigger phrases like "team review these tests", "consensus review the tests in PR.
researching-code
Use this skill when the user asks an architectural or semantic question about a codebase — phrases like "how does X work?", "what's the architecture?", "help me understand this codebase", "find all components that use Y", "trace the data flow from A to B", "where is feature Z handled", "I'm new to this code, where do…
dev-environment-bootstrapping
Use this skill when the user asks to bootstrap, set up, create, or initialize a Shopware development environment from scratch — phrases like "set up a Shopware dev environment", "clone and install Shopware", "initialize a Shopware plugin project", "bootstrap Shopware and a new plugin called X", "get a fresh Shopware…
phpunit-integration-to-unit-migrating
Use this skill ONLY when the user explicitly requests an audit, migration, or evaluation of whether a Shopware integration test belongs in the unit suite — trigger phrases like "audit integration tests", "migrate integration tests to unit", "is this an integration test or a unit test", "evaluate integration tests for…
cross-browser-typography-qa
Use this skill when web text looks clipped, flattened, wrapped incorrectly, misaligned, or materially different between Chromium and WebKit/Safari. Treat text rendering as both a geometry problem and a visual paint problem: passing DOM bounds does not prove that every glyph is intact.