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 adelaidasofia/claude-patterns --skill patternsgit clone --depth 1 https://github.com/adelaidasofia/claude-patternsWrote 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/adelaidasofia/claude-patterns/patterns)<a href="https://agentmods.dev/skills/adelaidasofia/claude-patterns/patterns"><img src="https://agentmods.dev/badge/skills/adelaidasofia/claude-patterns/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/adelaidasofia/claude-patterns/patterns"><img src="https://agentmods.dev/badge/skills/adelaidasofia/claude-patterns/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.00086 | $0.01566 |
| Opus 5.5 | $0.00034 | $0.00626 |
| Sonnet 5.5 | $0.00017 | $0.00313 |
| Haiku 4.5 | $0.00009 | $0.00157 |
Grade A, and why
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 1mo 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/patterns — Instinct Engine
You are extracting signal before it evaporates. This skill scans recent sessions and surfaces what's hardening into real insight, then proposes concrete captures.
Run this after a weekly review, after a heavy journaling session, or whenever the user says "I keep noticing..." or "this keeps coming up."
Headless / auto mode: If you are running in a cron job, background script, or --print session with no interactive user, skip Step 3's confirmation. Auto-capture all findings. Add (auto-captured — review and edit) as a note in any new files created. Proceed directly to Step 4 → Step 5.
First-run config
On first invocation, look for [VAULT]/.patterns-prefs.md. If it doesn't exist, ask:
- Last-session file path (where the most recent session summary lives, e.g.
Meta/Last Session.md, ornone) - Decision log path (e.g.
Meta/Decision Log.md, ornone) - Journal folder (e.g.
Journal/, ornone) - Drafts folder (where writing seeds get created, e.g.
Writing/Drafts/) - Concept folder (where new concept notes go, e.g.
Notes/Concepts/) - Changelog file (where pattern runs get logged, e.g.
Vault Changelog.md, ornone) - CLAUDE.md path (where rules get written, default
CLAUDE.mdat vault root)
Save preferences. Don't ask again.
Auto-Detection (session-end triggers)
At the end of every session (before the session-close checklist), Claude should silently evaluate whether the current session hit any of these four triggers. If one or more fires, surface it as a suggestion before closing.
Trigger 1: High tool-call friction The session required 5+ tool calls to accomplish something that should have been routine (e.g., finding a file, running a known workflow, looking up a fact that's in the vault). This suggests a missing shortcut, rule, or skill step. → "I noticed it took [N] steps to [task]. Want me to run /patterns to capture a shortcut?"
Trigger 2: User correction The user corrected Claude's approach during this session ("no, not that way", "don't do X", "use Y instead"). A feedback memory was likely saved, but there may be a deeper pattern if this correction echoes prior ones. → "You corrected me on [topic] this session. Want me to check if this is a recurring pattern worth capturing as a rule?"
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.
- 1mo ago First seen · 120 lines · 86 tokens per session scan A d85c7acecda9
patterns is a skill published in the GitHub repository adelaidasofia/claude-patterns (2 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 1,566 once invoked, about $0.0003 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
handoff
Generate a HANDOFF.md that captures goal, current state, files touched, failed attempts, and next steps — so a fresh Claude session can continue exactly where this one left off. Use when sessions are getting long, Claude keeps retrying the same broken solution, or the user wants to step away and resume later.
daily-briefing
Proactive daily briefing that fires on a recurring schedule, pulls recent memory and workspace context, composes a structured summary (action items, progress, radar, next steps), and delivers it to all active channels. Enable with a time like "set up my daily briefing at 9am". Disable, reschedule, or check status at…
identity-snapshot
Generate a living profile of the user's working patterns, decision tendencies and quality preferences from their Dex data. Use when the user says 'what are my patterns', 'how do I work', or during week-review. Also use proactively when the model (older than 7 days) is stale. Not for planning a week; use week-plan.
nav-compact
Clear conversation context while preserving knowledge via context marker. Use when user says "clear context", "start fresh", "done with this task", or when approaching token limits.
setup-brain
Set up or upgrade an AI-powered Obsidian vault. Interviews you, builds your vault structure (or works with what you already have), creates your CLAUDE.md memory file, installs tools, and gets you journaling — all in one conversation. Also has a repair/upgrade path for existing users.
second-brain-mapping
Use when the user wants to map or remap their second brain, refresh the vault's queryable metadata index, extract structured frontmatter from typed notes (books, meetings, people, journals, goals), fill wikilink gaps, or surface cross-type insights and patterns no single file shows. Triggers: /second-brain-mapping…