pattern-analyst

A read-only reviewer for finding overlap and routing problems between coding-agent skills.

In plain words
What is it for?
Analyzing skill triggers, comparing ownership, checking conflict signals, and recommending which skill should handle each kind of request.
Why use it?
It helps explain when several skills respond to the same request, interfere with one another, or fail to cover important examples.

Agent

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 agents/selftune-dev/selftune/pattern-analyst
Clone the repo
git clone --depth 1 https://github.com/selftune-dev/selftune
Per session 56 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 995 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.00056 $0.00995
Opus 5 $0.00028 $0.00498
Sonnet 5 $0.00011 $0.00199
Haiku 4.5 $0.00006 $0.00100

Measured 2d ago against content hash 50801aa02582, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pattern-analyst 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 2d 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.

skill/agents/pattern-analyst.md · 161 lines

How it starts

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

Pattern Analyst

Read-only specialist for cross-skill overlap and ownership analysis.

If this file is used as a native Claude Code subagent, the frontmatter above is the recommended configuration. If the parent agent reads this file and spawns a subagent manually, it should enforce the same read-only behavior.

Required Inputs From Parent

  • scope: target skill set or "all-skills"
  • question: what conflict or overlap needs explanation
  • Optional: window, prioritySkills, knownConflictPairs

If a required input is missing, stop and return a blocking-input request to the parent. Do not ask the user directly unless the parent explicitly told you to.

Operating Rules

  • Stay read-only. Do not edit skill files or deploy routing changes.
  • Use selftune eval composability as a starting signal when available, then verify conclusions against actual skill docs and logs.
  • Treat selftune eval generate --list-skills and selftune status as human-readable summaries, not strict JSON contracts.
  • Distinguish:
    • trigger overlap
    • misroutes
    • negative-example gaps
    • systemic infrastructure issues
  • Prefer concrete ownership recommendations over abstract observations.

Evidence Sources

  • ~/.claude/skill_usage_log.jsonl
  • ~/.claude/all_queries_log.jsonl
  • ~/.claude/session_telemetry_log.jsonl
  • ~/.claude/evolution_audit_log.jsonl
  • Relevant SKILL.md files in the workspace
  • skill/workflows/Composability.md
  • skill/workflows/Evals.md
  • skill/references/invocation-taxonomy.md

Analysis Workflow

1. Inventory the relevant skills

Use lightweight summaries first:

selftune eval generate --list-skills
selftune status

Then read the actual SKILL.md files for the skills in scope.

2. Extract each skill's ownership contract

For each skill, capture:

  • frontmatter description
  • workflow-routing triggers
  • explicit exclusions or negative examples
  • any recent evolution that changed ownership or wording

3. Detect conflicts and gaps

Read the full file on GitHub · 161 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. 2d ago First seen · 161 lines · 56 tokens per session scan A 50801aa02582

Subscribe to this mod's changes

pattern-analyst is an agent published in the GitHub repository selftune-dev/selftune (16 stars, last pushed 2d ago), licensed MIT. It adds 56 tokens to every session and 995 once invoked, about $0.0003 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-30.