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 synaptiai/synapti-marketplace --skill code-quality-principlesgit clone --depth 1 https://github.com/synaptiai/synapti-marketplaceWrote 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/synaptiai/synapti-marketplace/code-quality-principles)<a href="https://agentmods.dev/skills/synaptiai/synapti-marketplace/code-quality-principles"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/code-quality-principles/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/synaptiai/synapti-marketplace/code-quality-principles"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/code-quality-principles.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.00083 | $0.00960 |
| Opus 5.5 | $0.00033 | $0.00384 |
| Sonnet 5.5 | $0.00017 | $0.00192 |
| Haiku 4.5 | $0.00008 | $0.00096 |
Grade A, and why
code-quality-principles 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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Quality Principles
Iron Law
EVERY CHANGE MUST BE INTENTIONAL. If you can't explain why a line changed, revert it.
Before You Write Code
Answer first, or return to EXPLORE: which task/criterion this code serves; which files change and why each; which existing project patterns apply; what could go wrong (error cases, edge cases, security); how you will verify it.
Boy Scout Rule
Leave every file you touch better than you found it. Touching a file means owning its known issues.
The proximity test is NOT a deferral mechanism for P1/P2 findings. It decides how a cleanup is committed (alongside the feature fix vs. a separate improve: commit), not whether it gets fixed. A P1 or P2 in a file the PR modifies is fixed in this PR.
A cleanup is a standalone improve: commit when ALL true:
- The file is already being modified for the current task
- The fix is self-evidently correct (lint, format, typo, obvious bug, missing error handling)
- The fix is small (under ~10 lines)
- It does not change public API signatures or behavior semantics
- It needs no explanation beyond "Boy Scout cleanup"
A finding requires expanded scope (still fixed; may need a design note or tests) when ANY true:
- Requires modifying files NOT already touched by the task
- Changes architecture, module boundaries, or public APIs
- Requires new tests to validate
- Would benefit from its own issue to explain motivation
- Is a subjective style preference (P3 at most, not a fix-blocker)
P1/P2 in the expanded-scope bucket: fix in-PR with an appropriate commit message. Finding triage is NEVER a valid escalation trigger — do NOT file a six-field escalation to ask whether to fix a finding (see skills/llm-operator-principles/SKILL.md and references/escalation-format.md). "Disagree to fix" and "ask the user whether to fix" are not options.
Default mode: cosmetic P3 in truly untouched files is fixed if bounded (<10 lines) or documented inline in the PR body. Do NOT create follow-up issues for them.
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 Changed · -52 lines 41e8ef5b8bef
- 1mo ago First seen · 122 lines · 83 tokens per session scan A 0777da595d9a
code-quality-principles is a skill published in the GitHub repository synaptiai/synapti-marketplace (7 stars, last pushed 12d ago), licensed Apache-2.0. It adds 83 tokens to every session and 960 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-09-03.
Other skills, from other repositories
check
Confirm a change before merge. /check verify drives the real app to prove behavior against the spec (every acceptance criterion met, every surface built). /check review runs a senior code review on a fresh model, one that did not write the code. Verify after /develop, review before a PR. Writes to docs/reviews/, never…
backlog
Seed a backlog from the project's documents: the Product Owner reads docs/ (plus the constitution and ROADMAP.md), proposes an ordered list of feature-sized items each traced to a source section, the user edits the list, and on explicit confirmation each item is filed as a GitHub issue that /story-time can import. Use…
architect
Produces Alon's design-doc system before code: SOURCEOFTRUTH.md, ARCHITECTUREROADMAP.md, TODOWORKFLOW.md, CLAUDE.md, plus a modular docs/architecture set for larger projects. Model first: data and invariants before framework, every invariant enforced at two boundaries, failure paths designed as deliberately as happy…
next-steps
Have the Product Owner survey the project's current state — shipped features, in-flight work, open findings, standing goals — and propose one concrete next feature ready to hand to /story-time or /spark. Use when the user has no idea in hand and asks "what should we build next", when a loop just closed and the next…
x-spec
A system-planning guide that turns a vague idea into a set of linked design documents. It defines goals, modules, interfaces, data, workflows, and ways to check the result.
increment
Start the Act phase of the SPARK loop: build the increment strictly following the approved plan, task by task, with progress tracked in the plan. Use after the plan is approved, or to fix findings that came back from /peer-review or /demo-day.