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 skills add denenis-lab/my-claude-skills --skill analyze-patternsgit clone --depth 1 https://github.com/denenis-lab/my-claude-skillsWrote 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/skills/denenis-lab/my-claude-skills/analyze-patterns)<a href="https://agentmods.dev/skills/denenis-lab/my-claude-skills/analyze-patterns"><img src="https://agentmods.dev/badge/skills/denenis-lab/my-claude-skills/analyze-patterns/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.
<a href="https://agentmods.dev/skills/denenis-lab/my-claude-skills/analyze-patterns"><img src="https://agentmods.dev/badge/skills/denenis-lab/my-claude-skills/analyze-patterns.svg" alt="Reviewed on agentmods" width="80" 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.00021 | $0.00891 |
| Opus 5.5 | $0.00008 | $0.00356 |
| Sonnet 5.5 | $0.00004 | $0.00178 |
| Haiku 4.5 | $0.00002 | $0.00089 |
Grade A, and why
analyze-patterns 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.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Patterns
When the user invokes /analyze-patterns or says "analyze sessions" / "find patterns":
Step 1: Extract messages from sessions
Run the extractor script, save to a temp file:
# Incremental (only new sessions since last run):
python3 ~/.claude/skills/analyze-patterns/scripts/pattern-detector.py --user-only --stats > /tmp/pattern-extract.json
# Or full rescan (all sessions):
python3 ~/.claude/skills/analyze-patterns/scripts/pattern-detector.py --full --user-only --stats > /tmp/pattern-extract.json
Use --full if the user says "all sessions" / "full" / "--full".
Default is incremental. The --user-only flag extracts only user messages (smaller output).
Read /tmp/pattern-extract.json — it contains JSON with this structure:
{
"session_count": 124,
"projects": {
"ProjectName": {
"message_count": 25,
"user_count": 25,
"messages": [{"role": "user", "text": "..."}]
}
}
}
IMPORTANT: The file can be large (~400-500 KB). Read project by project, analyzing the largest ones first.
Step 2: Analyze patterns
Read the script output and find 4 types of patterns:
1. REPEATED_CORRECTION
User corrects Claude the same way in 2+ different sessions. Examples: "write shorter", "don't ask for confirmation", "use bun". → Suggestion: add to CLAUDE.md or create a rule file
2. FREQUENT_TOOL
The same workflow/skill/tool is used frequently. Examples: constantly calls /browser, always runs the same test command. → Suggestion: create an auto-trigger or shortcut
3. ABANDONED_TASK
Work started but not finished, errors left unfixed. Examples: config change started — session ended, bug found — not fixed. → Suggestion: create an issue to complete the work
4. CLAUDE_RESISTANCE
Claude didn't understand or the user had to explain again. Examples: Claude asks permission when told not to, writes in the wrong language. → Suggestion: improve the prompt/rule
Step 3: Show results to the user
For each pattern found, show:
- Type (REPEATED_CORRECTION / FREQUENT_TOOL / ABANDONED_TASK / CLAUDE_RESISTANCE)
- Short title
- Evidence quotes from user messages
- Specific action suggestion
- Priority (high / medium / low)
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 126 lines · 21 tokens per session scan A bd509f077061
analyze-patterns is a skill published in the GitHub repository denenis-lab/my-claude-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 21 tokens to every session and 891 once invoked, about $0.0001 per session on Opus 5.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.
Other skills, from other repositories
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
Freelance Empire
Complete freelance business operating system — from first client to six-figure solo business. Covers positioning, pricing, proposals, client management, finances, scaling, and the transition from side-hustle to full-time. Use when starting freelancing, raising rates, managing clients, building recurring revenue, or…
AI Recruiting Engine
Full-cycle recruiting agent — source, screen, score, and hire top talent with structured frameworks, scorecards, and pipeline automation. Zero dependencies.
agent-council
Complete toolkit for creating autonomous AI agents and managing Discord channels for OpenClaw. Use when setting up multi-agent systems, creating new agents, or managing Discord channel organization.
agent-swarm-workflow
Jeffrey Emanuel's multi-agent implementation workflow using NTM, Agent Mail, Beads, and BV. The execution phase that follows planning and bead creation. Includes exact prompts used.
agi-farm
Interactive setup wizard that creates a fully working multi-agent AI team on OpenClaw. One command bootstraps agents, SOUL.md personas, comms infrastructure (inboxes/outboxes/broadcast), cron jobs, auto-dispatcher (HITL + rate-limit backoff + dependency checking), and a portable GitHub bundle — all customized to team…