A quality-check command that reads the current copywriting phase and runs the checks required for that phase.

Use it to validate research, briefing, production, or delivered work, including file checks, specialist reviews, and human approval where required.

It replaces a manual checklist with a structured gate that reports passed items, failures, and whether the work should advance.

validate — Command for Claude Code by lckx777

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.

Clone the repo

git clone --depth 1 https://github.com/lckx777/copy-chief-black

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/lckx777/copy-chief-black/validate/github.svg)](https://agentmods.dev/commands/lckx777/copy-chief-black/validate)

Your own site

<a href="https://agentmods.dev/commands/lckx777/copy-chief-black/validate"><img src="https://agentmods.dev/badge/commands/lckx777/copy-chief-black/validate/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/lckx777/copy-chief-black/validate"><img src="https://agentmods.dev/badge/commands/lckx777/copy-chief-black/validate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 302 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.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00302
Opus 5	$0.00000	$0.00151
Sonnet 5	$0.00000	$0.00060
Haiku 4.5	$0.00000	$0.00030

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

Security

Grade A, and why

validate 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 7d 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.

framework/commands/validate.md · 30 lines

What it actually says

/validate — Run Quality Gate for Current Phase

Read the active offer's helix-state.yaml to determine current phase, then:

Load the appropriate task file from ~/.claude/tasks/:
- RESEARCH phase → ~/.claude/tasks/research-quality-gate.md
- BRIEFING phase → ~/.claude/tasks/briefing-quality-gate.md
- PRODUCTION phase → ~/.claude/tasks/production-quality-gate.md
- DELIVERED phase → ~/.claude/tasks/delivery-quality-gate.md
Read the task file completely.
Create a TaskCreate checklist with ALL steps from the task file.
Execute each step sequentially:
- For file verification steps: use Glob/Read to check existence
- For MCP steps: use the appropriate MCP tool (validate_gate, blind_critic, etc)
- For human approval: use AskUserQuestion
After all steps, present a summary:
- PASSED items (with scores where applicable)
- FAILED items (with specific feedback)
- RECOMMENDATION: advance phase or fix issues

If no offer is detected, show error and suggest /status or ecosystem-guide.

Arguments:

$ARGUMENTS can specify offer path: /validate concursos/decifra-lei-seca
If no argument, detect from current-offer.json or most recent offer

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.

7d ago First seen · 30 lines · 0 tokens per session scan A 2e8bf4513de2

Subscribe to this mod's changes

validate is a command published in the GitHub repository lckx777/copy-chief-black (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 302 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.

Testing

prototype

You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.

grainulation/grainulator · 0 tokens

verify

Run repository verification using the verification-loop skill.

cloudnative-co/claude-code-starter-kit · 9 tokens

qa-changes

This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…

OpenHands/extensions · 63 tokens

validate