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 skills/lis186/sourceatlas/pattern-findernpx skills add lis186/SourceAtlas --skill pattern-findergit clone --depth 1 https://github.com/lis186/SourceAtlasWhat 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 | $0.00054 | $0.00350 |
| Opus 5 | $0.00027 | $0.00175 |
| Sonnet 5 | $0.00011 | $0.00070 |
| Haiku 4.5 | $0.00005 | $0.00035 |
Grade A, and why
pattern-finder 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.
What it actually says
Pattern Finder
When to Use
Trigger this skill when the user:
- Asks how to implement a specific feature
- Wants to see existing implementation examples
- Needs to follow project conventions
- Asks "how does this project do X"
- Asks "show me examples of X"
Instructions
- Identify what pattern the user is looking for
- Run
/sourceatlas:pattern "<pattern>"with the relevant pattern name - Returns best example files with line numbers and implementation guide
Common Patterns
- API endpoints:
/sourceatlas:pattern "api endpoint" - Authentication:
/sourceatlas:pattern "authentication" - Database queries:
/sourceatlas:pattern "database query" - Background jobs:
/sourceatlas:pattern "background job" - File uploads:
/sourceatlas:pattern "file upload" - Error handling:
/sourceatlas:pattern "error handling" - Validation:
/sourceatlas:pattern "validation" - Testing:
/sourceatlas:pattern "unit test"
What User Gets
- Best example files with exact line numbers
- Standard implementation flow
- Key conventions to follow
- Common pitfalls to avoid
- Testing patterns
Example Triggers
- "How do I add a new API endpoint?"
- "Show me how authentication works here"
- "Where can I find examples of database queries?"
- "How does this project handle errors?"
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.
- 2d ago First seen · 48 lines · 54 tokens per session scan A 36019b418d60
pattern-finder is a skill published in the GitHub repository lis186/SourceAtlas (47 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 350 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.