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 3yesore/LetUenforskills --skill asa-reuse-pattern-minergit clone --depth 1 https://github.com/3yesore/LetUenforskillsWrote 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/3yesore/letuenforskills/asa-reuse-pattern-miner)<a href="https://agentmods.dev/skills/3yesore/letuenforskills/asa-reuse-pattern-miner"><img src="https://agentmods.dev/badge/skills/3yesore/letuenforskills/asa-reuse-pattern-miner/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/3yesore/letuenforskills/asa-reuse-pattern-miner"><img src="https://agentmods.dev/badge/skills/3yesore/letuenforskills/asa-reuse-pattern-miner.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.00029 | $0.01043 |
| Opus 5 | $0.00015 | $0.00522 |
| Sonnet 5 | $0.00006 | $0.00209 |
| Haiku 4.5 | $0.00003 | $0.00104 |
Grade A, and why
asa-reuse-pattern-miner 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 11d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ASA Reuse Pattern Miner
Use this internal meta-skill when a model must convert one or more analyzed skills into reusable design assets.
This skill fixes the failure mode where pattern mining becomes a loose summary instead of reusable anchors, composition candidates, anti-patterns, and optional solidification templates that another author can apply.
Inputs
- Skill summaries and source paths.
- Structure analysis, workflow analysis, and reviewer outputs.
- Resource roles, workflow steps, evidence strength, and reusable artifacts.
- Optional model comparison notes when available.
Process
- Identify mechanisms that can transfer beyond one repository.
- Separate concrete implementation details from reusable design principles.
- For each candidate pattern, write problem, solution, when-to-use, counterexample, and evidence.
- Mark pattern maturity as
candidate,emerging, orestablishedbased on example count and mechanism similarity. - Extract checklists only when steps are actionable.
- Extract templates only when placeholders and usage boundaries are clear.
- Record anti-patterns when the source exposes a likely failure mode.
- Convert transferable mechanisms into reuse, composition-candidate, anti-pattern, and solidification-template anchors.
- Avoid copying source text; abstract the method and point back to evidence.
Output Contract
Return reusable assets suitable for patterns.json and Obsidian notes:
reuse_assets:
patterns: []
templates: []
checklists: []
anti_patterns: []
extension_ideas: []
anchors:
reuse_anchor:
- id:
name:
problem:
reusable_mechanism:
when_to_use: []
when_not_to_use: []
source_patterns: []
reuse_modes:
- reference_only
- temporary_composition
- prompt_patch
- workflow_step
- learning_note
portability: high | medium | low
confidence: high | medium | low | unknown
evidence: []
composition_candidate_anchor:
- id:
name:
selected_anchors: []
composition_form: reference_only | temporary_composition | prompt_patch | agent_rule_patch | workflow_insert | tool_adapter | template_pack | quality_gate | learning_note | full_workflow_blueprint | new_skill_spec
user_goal:
expected_output:
required_adapters: []
conflict_risks: []
preserve_existing_skills: true
solidification_required: true | false
confidence: high | medium | low | unknown
evidence: []
anti_pattern_anchor:
- id:
name:
failure_mode:
appears_when: []
avoid_by: []
affected_anchor_types: []
severity: high | medium | low
evidence: []
solidification_template_anchor:
- id:
name:
target_form: full_workflow_blueprint | new_skill_spec | template_pack | quality_gate
use_only_when: []
required_sections: []
required_anchors: []
optional_anchors: []
non_destructive_output:
rollback_note:
evidence: []
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.
- 11d ago First seen · 133 lines · 29 tokens per session scan A bfc3d08a90e8
asa-reuse-pattern-miner is a skill published in the GitHub repository 3yesore/LetUenforskills (2 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 1,043 once invoked, about $0.0001 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-31.
Other skills, from other repositories
link-memory
Use after important user-approved decisions, when durable context should be proposed or reviewed, and for explicit Link memory lifecycle work: remember, recall, review, update, archive, restore, forget, or explain local memories through the CLI without requiring MCP.
link-retrieve
Use before answering work that may depend on user memory, project history, source-backed notes, or prior decisions; retrieve compact Link context through the CLI without loading the whole wiki or requiring MCP.
link-health
Use at the start of Link work when readiness is unclear, after installs or upgrades, and before repairs; verify health, inspect interrupted writes, back up, and repair generated indexes without MCP.
link-ingest
Use when raw files are present, source pages look stale, or a user asks to ingest notes into Link; refresh source-backed wiki pages, propose memories, and validate updates through the CLI without MCP.
kb
Use when compiling raw sources into the wiki, querying the knowledge base, running health checks or lint on the wiki, evolving or improving wiki coverage, or when user says 'compile', 'update the wiki', 'query', 'lint', 'health check', 'evolve', 'what's missing', or 'suggest improvements'. Also triggers on questions…
kb-init
Use when setting up a new knowledge base, bootstrapping an Obsidian vault, or when user says 'init kb', 'new knowledge base', 'create kb', or 'setup vault'. Triggers on any request to initialize or scaffold a knowledge base project.