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.
npx agentmods add commands/justinperea/midjourney-cc-skill/validate-patterngit clone --depth 1 https://github.com/JustinPerea/midjourney-cc-skillWrote 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.
[](https://agentmods.dev/commands/justinperea/midjourney-cc-skill/validate-pattern)<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="Measured on agentmods" height="20"></a>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 | $0.00000 | $0.00270 |
| Sonnet 5 | $0.00000 | $0.00108 |
| Haiku 4.5 | $0.00000 | $0.00054 |
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 5d 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.
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 sessionsvia sqlite-simple MCP. If the query fails, tell the user: "Database not available. Runclaude mcp add sqlite-simple -- npx @anthropic-ai/sqlite-simple-mcp mydatabase.dbthen 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
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.
- 5d ago First seen · 53 lines · 0 tokens per session scan A 62afbbbc9999
validate-pattern is a command published in the GitHub repository JustinPerea/midjourney-cc-skill (11 stars, last pushed 6mo 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.