sk-code-quality

sk-code-quality is a skill for Claude Code, OpenCode from MichelKerkmeester/skilled-agent-harness_spec-driven-loops. It costs 0 tokens per session (5,145 once invoked), scanned A, original, MIT.

A quality-check workflow for changed code, scripts, skills, agents, commands, servers, and specification documents.

In plain words
What is it for?
Use it after implementation to check and fix quality problems in OpenCode files, Webflow code, and other supported project files.
Why use it?
It catches author-side problems before verification or completion, including risky changes, poor comments, and surface-specific issues.

Skill for Claude CodeOpenCode

Written for Claude Code and OpenCode: allowed-tools in frontmatter, but also installed under .opencode/. Also seen: mentions subagents; mentions OpenCode.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is +- Surface identity -> ../shared/references/stack-detection.md.

Good fit Use it after implementation to check and fix quality problems in OpenCode files, Webflow code, and other supported project files.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/MichelKerkmeester/skilled-agent-harness_spec-driven-loops
agentmods
npx agentmods add skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/sk-code-quality

Made for: Claude Code, OpenCode.

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 sk-code-quality

README.md
[![agentmods](https://agentmods.dev/badge/skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/sk-code-quality/github.svg)](https://agentmods.dev/skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/sk-code-quality)
Your own site
<a href="https://agentmods.dev/skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/sk-code-quality"><img src="https://agentmods.dev/badge/skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/sk-code-quality/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 sk-code-quality

Your own site · 80×15
<a href="https://agentmods.dev/skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/sk-code-quality"><img src="https://agentmods.dev/badge/skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/sk-code-quality.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,145 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
SkillSpector: 1 finding, up to low

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • low Excessive Agency · line 248
    Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.
    Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00000 $0.05145
Opus 5 $0.00000 $0.02573
Sonnet 5 $0.00000 $0.01029
Haiku 4.5 $0.00000 $0.00515

Measured 6d ago against content hash 7d2e61eb66ff, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

sk-code-quality 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 6d ago.

The scan reads SKILL.md. This mod also ships 5 executable files (scripts/check-comment-hygiene.sh, scripts/check-comment-hygiene.test.sh, scripts/check-dist-staleness.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.opencode/skills/sk-code/sk-code-quality/SKILL.md · 324 lines

How it starts

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

Code Quality (quality)

quality is the author-side quality gate MODE child of the sk-code family. It runs after the surface skill (code-webflow / code-opencode) implements changes and before the surface's verification workflow or done-claim. It consumes the shared surface router, loads the right checklist for the detected surface and target path, fixes quality-gate failures in place, and leaves findings-only output to code-review.


1. WHEN TO USE

Activation Triggers

Use this mode when the request involves:

  • Running the post-implementation quality gate before a completion claim.
  • Applying P0/P1/P2 author-side checks to changed code, scripts, skills, agents, commands, MCP servers, or spec docs.
  • Checking comment hygiene on modified files and removing ephemeral artifact references from comments while preserving durable WHY.
  • Loading an OpenCode authoring checklist for .opencode/skills/, .opencode/agents/, .opencode/commands/, .opencode/specs/, MCP server source, or language-specific OpenCode files.
  • Applying Webflow/frontend quality standards after implementation and before runtime verification.
  • Fixing quality-gate failures in place with Edit when the fix belongs to the already-authored file.

Keyword triggers: quality gate, code quality, comment hygiene, surface checklist, P0, P1, P2, authoring checklist, OpenCode checklist, skill authoring, agent authoring, command authoring, MCP server authoring, spec folder authoring, check before done.

When NOT to Use

Skip this mode when:

  • The user needs code written, files scaffolded, or behavior implemented. Use the appropriate surface skill (code-webflow / code-opencode) and its implementation workflow.
  • A failure needs symptom-to-root-cause investigation or a single-cause bug fix. Use the surface's debugging workflow (workflow-debug.md).
  • The task is to collect final non-mutating verification evidence. Use the surface's verification workflow (workflow-verify.md).
  • The user asks for findings-first review output, severity-ranked findings, or PR review. Use code-review.
  • The task is documentation-only prose with no code-work contract. Use sk-doc.

Read the full file on GitHub · 324 lines

Files

What ships with it

31 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. 6d ago First seen · 324 lines · 0 tokens per session scan A 7d2e61eb66ff

Subscribe to this mod's changes

sk-code-quality is a skill published in the GitHub repository MichelKerkmeester/skilled-agent-harness_spec-driven-loops (35 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,145 tokens. 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.

Related

Other skills, from other repositories

adversarial-reviewer

Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.

emdash-cms/emdash · 71 tokens

gsd-ns-review

Route to the appropriate quality / review skill based on the user's intent. gsd-code-review-fix was absorbed by gsd-code-review --fix in #2790.

open-gsd/gsd-core · 16 tokens

issue

Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…

jeremylongshore/tons-of-skills-marketplace · 115 tokens

gitnexus

A code-graph analysis add-on for examining an existing codebase, including symbols, call paths, execution flows, and effects across repositories. It can query GitNexus through its command-line or MCP interfaces.

hashgraph-online/awesome-codex-plugins · 58 tokens

cleanup-code-inspections

Reduce technical debt and improve code quality by systematically resolving static analysis warnings.

flutter/flutter-intellij · 19 tokens

superlint

This skill describes the mandatory standard operating procedure for using our internal SuperLint tool. Use this when tasks require fixing code quality issues according to corporate standards.

mgechev/skillgrade · 0 tokens