zero-script-qa

A compatibility command for the toolkit’s `/qa` quality-check command. QA means checking that software builds, tests, and behaves as expected, including by inspecting logs.

In plain words
What is it for?
It helps run build, test, log, and summary checks, then continue with code review or PDCA analysis.
Why use it?
It gives an alternate command name for the same quality-check workflow. It also lays out an order for build, test, log, summary, and follow-up review checks.

Command

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 commands/demodev-lab/claude-code-plugin-demokit/zero-script-qa
Clone the repo
git clone --depth 1 https://github.com/demodev-lab/claude-code-plugin-demokit
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 185 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.00035 $0.00185
Opus 5 $0.00017 $0.00093
Sonnet 5 $0.00007 $0.00037
Haiku 4.5 $0.00003 $0.00018

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

Security

Grade A, and why

zero-script-qa 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.

commands/zero-script-qa.md · 30 lines

What it actually says

/zero-script-qa (Compatibility Alias)

/zero-script-qa는 demokit의 /qa와 동일한 목적의 호환 명령입니다.

사용 가이드

  • 빌드 점검: /qa build
  • 테스트 점검: /qa test
  • 로그 점검: /qa log
  • 종합 리포트: /qa summary

권장 흐름

  1. /qa build
  2. /qa test
  3. /qa log
  4. /qa summary
  5. /review 또는 /pdca analyze <feature>
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 · 30 lines · 35 tokens per session scan A dbc443e3c7d6

Subscribe to this mod's changes

zero-script-qa is a command published in the GitHub repository demodev-lab/claude-code-plugin-demokit (2 stars, last pushed 6mo ago), licensed MIT. It adds 35 tokens to every session and 185 once invoked, about $0.0002 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.