What is validate-pattern?

A command for recording whether a previously identified pattern worked again, failed, or was not clearly relevant. It stores the new evidence and updates the pattern’s statistics in a database.

Use it to select a pattern, record the outcome and context of a new test, and update its supporting evidence.

It gives repeated observations a record instead of leaving pattern confidence based only on memory or a single result.

How JustinPerea/midjourney-cc-skill configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to JustinPerea/midjourney-cc-skill. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/JustinPerea/midjourney-cc-skill/main/.claude/commands/validate-pattern.md

Clone the repo

git clone --depth 1 https://github.com/JustinPerea/midjourney-cc-skill

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/justinperea/midjourney-cc-skill/validate-pattern/github.svg)](https://agentmods.dev/commands/justinperea/midjourney-cc-skill/validate-pattern)

Your own site

<a href="https://agentmods.dev/commands/justinperea/midjourney-cc-skill/validate-pattern"><img src="https://agentmods.dev/badge/commands/justinperea/midjourney-cc-skill/validate-pattern/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/justinperea/midjourney-cc-skill/validate-pattern"><img src="https://agentmods.dev/badge/commands/justinperea/midjourney-cc-skill/validate-pattern.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 540 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.00540
Opus 5.5	$0.00000	$0.00216
Sonnet 5.5	$0.00000	$0.00108
Haiku 4.5	$0.00000	$0.00054

Measured 2mo ago against content hash 62afbbbc9999, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

validate-pattern 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 2mo 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.

.claude/commands/validate-pattern.md · 53 lines

How it starts

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

Validate Pattern

Mark a pattern as validated (worked again) or contradicted (failed) based on new evidence.

Instructions

Verify database access. Run SELECT COUNT(*) FROM sessions via sqlite-simple MCP. If the query fails, tell the user: "Database not available. Run claude mcp add sqlite-simple -- npx @anthropic-ai/sqlite-simple-mcp mydatabase.db then restart Claude Code." Do not proceed without database access.
Identify the pattern. The user may provide:
- A pattern ID directly
- A description of the pattern
- If unclear, show active patterns and let them pick:
```
SELECT id, category, problem, solution, confidence FROM patterns WHERE is_active = 1 ORDER BY category, confidence DESC
```
Ask for the outcome:
- Did the pattern work as expected? (supported)
- Did it fail or produce wrong results? (contradicted)
- Was it not clearly relevant? (neutral)
Get context: Ask which session this relates to, or if it's a general observation.

Record the evidence:

INSERT INTO pattern_evidence (pattern_id, session_id, iteration_id, outcome, notes) VALUES (?, ?, ?, ?, ?)

Update the pattern stats:

UPDATE patterns SET
  times_tested = times_tested + 1,
  times_succeeded = times_succeeded + CASE WHEN ? = 'supported' THEN 1 ELSE 0 END,
  success_rate = CAST(times_succeeded AS REAL) / times_tested,
  last_validated_at = CASE WHEN ? = 'supported' THEN datetime('now') ELSE last_validated_at END,
  last_failed_at = CASE WHEN ? = 'contradicted' THEN datetime('now') ELSE last_failed_at END
WHERE id = ?

Update confidence if warranted:
- If success_rate drops below threshold for current confidence, lower it
- If enough new tests support it, raise it
- Apply the confidence rules from the skill guide
If contradicted, flag for attention:
- Show the user the contradiction
- Ask if the pattern should be updated, kept as-is, or deactivated
- If the contradiction reveals a more nuanced pattern (works in context A but not B), suggest splitting the pattern

Read the full file on GitHub · 53 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.

2mo ago First seen · 53 lines · 0 tokens per session scan A 62afbbbc9999

Subscribe to this mod's changes

validate-pattern is a command published in the GitHub repository JustinPerea/midjourney-cc-skill (16 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 540 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-08-31.

Analytics and metrics

validate-pattern next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
validate-patternJustinPerea/midjourney-cc-skill	Command	16	9mo ago	MIT	A	0	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

midjourney-cc-skill: Command for Claude Code