quality-gate

An automated set of checks for JavaScript and TypeScript projects, including code quality checks and a security scan before pushing changes to Git.

In plain words
What is it for?
Running checks on changed files when a session stops and scanning git push commands with tools for code security and exposed credentials.
Why use it?
It catches type errors, lint errors, failing tests, possible dead code, circular dependencies, unfinished markers, and leaked secrets before changes are accepted.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/iwritec0de/app-dev/quality-gate
Any agent
npx skills add iwritec0de/app-dev --skill quality-gate
Clone the repo
git clone --depth 1 https://github.com/iwritec0de/app-dev

Made for: Claude Code, Codex.

Per session 115 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 770 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00115 $0.00770
Opus 5 $0.00057 $0.00385
Sonnet 5 $0.00023 $0.00154
Haiku 4.5 $0.00012 $0.00077

Measured yesterday against content hash a7897848b254, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

quality-gate 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 yesterday.

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.

skills/quality-gate/SKILL.md · 78 lines

How it starts

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

Quality Gate

Automated quality enforcement with two hooks:

Stop Hook — Code Quality

Fires on every session stop. Runs JavaScript/TypeScript checks on changed files:

Check Tool Severity
Types tsc --noEmit BLOCK
Lint eslint BLOCK on errors, WARN on warnings
Format prettier --check WARN
Tests jest BLOCK
Dead code knip (unused exports, deps, files) WARN
Type coverage type-coverage (>80% threshold) WARN
Circular deps madge --circular WARN
TODO/FIXME grep scanner WARN

Behavior:

  • Missing required tools (tsc, eslint, prettier, jest) = FAIL with install command
  • Missing optional tools (knip, type-coverage, madge) = WARN with install suggestion
  • Retry limiter: allows stop after 3 consecutive failures

PreToolUse Hook — Security Scan

Intercepts git push commands. Runs 4 scanners in sequence:

  1. semgrep — SAST scan on changed files with --config=auto

    • Critical/High findings = BLOCK push
    • Medium findings = WARN
    • Claude should auto-fix findings before retrying
  2. gitleaks — scans commits being pushed for leaked secrets

    • Any secret found = BLOCK push
  3. trivy — filesystem vulnerability, secret, and misconfig scan

    • Critical vulns = BLOCK push
    • High vulns = WARN
  4. SonarQube (optional) — checks quality gate status if configured

    • Requires SONARQUBE_URL and SONARQUBE_TOKEN env vars, plus sonar-project.properties
    • Skipped silently if SONARQUBE_TOKEN is not set
    • Failed quality gate = BLOCK push

Configuration

Env Var Default Purpose
CLAUDE_QUALITY_GATE 1 Enable/disable quality gate
CLAUDE_QUALITY_GATE_MAX_RETRIES 3 Max retry attempts before allowing stop
SONARQUBE_URL https://sonarqube.internal SonarQube server URL
SONARQUBE_TOKEN (none) SonarQube auth token
CLAUDE_NOTIFY_DISCORD 0 Send Discord notifications
DISCORD_WEBHOOK_URL (none) Discord webhook for notifications

Read the full file on GitHub · 78 lines

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. yesterday First seen · 78 lines · 115 tokens per session scan A a7897848b254

Subscribe to this mod's changes

quality-gate is a skill published in the GitHub repository iwritec0de/app-dev (3 stars, last pushed 4mo ago), licensed MIT. It adds 115 tokens to every session and 770 once invoked, about $0.0006 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.

Related

Other skills, from other repositories

dummy-dataset

Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.

phuryn/pm-skills · 48 tokens

outcome-roadmap

Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.

phuryn/pm-skills · 53 tokens

release-notes

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.

phuryn/pm-skills · 57 tokens

retro

Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.

phuryn/pm-skills · 52 tokens

shipping-artifacts

The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded…

phuryn/pm-skills · 120 tokens

stakeholder-map

Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.

phuryn/pm-skills · 47 tokens