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 lis186/SourceAtlas --skill pattern-findergit clone --depth 1 https://github.com/lis186/SourceAtlasWrote 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/lis186/sourceatlas/pattern-finder)<a href="https://agentmods.dev/skills/lis186/sourceatlas/pattern-finder"><img src="https://agentmods.dev/badge/skills/lis186/sourceatlas/pattern-finder/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/lis186/sourceatlas/pattern-finder"><img src="https://agentmods.dev/badge/skills/lis186/sourceatlas/pattern-finder.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.00054 | $0.00350 |
| Opus 5.5 | $0.00022 | $0.00140 |
| Sonnet 5.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 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.
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.
- 1mo ago First seen · 48 lines · 54 tokens per session scan A 36019b418d60
pattern-finder is a skill published in the GitHub repository lis186/SourceAtlas (48 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 350 once invoked, about $0.0002 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-30.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…