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-trigger-boundary-mappergit 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-trigger-boundary-mapper)<a href="https://agentmods.dev/skills/3yesore/letuenforskills/asa-trigger-boundary-mapper"><img src="https://agentmods.dev/badge/skills/3yesore/letuenforskills/asa-trigger-boundary-mapper/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-trigger-boundary-mapper"><img src="https://agentmods.dev/badge/skills/3yesore/letuenforskills/asa-trigger-boundary-mapper.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.00801 |
| Opus 5 | $0.00015 | $0.00400 |
| Sonnet 5 | $0.00006 | $0.00160 |
| Haiku 4.5 | $0.00003 | $0.00080 |
Grade A, and why
asa-trigger-boundary-mapper 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ASA Trigger Boundary Mapper
Use this internal meta-skill when a model must determine when a skill should be invoked, when it should not be invoked, and what boundary conditions limit safe use.
This skill fixes the failure mode where an analyst treats examples, keywords, or broad domain terms as universal triggers.
Inputs
SKILL.mdfrontmatter description.- Body sections that mention "use when", "do not", warnings, constraints, or task scope.
- Deterministic content blocks with line references.
- Existing structure analysis context when available.
Process
- Extract explicit trigger text exactly when source wording says when to use the skill.
- Identify semantic triggers from task shape, but mark them inferred.
- Identify negative triggers and non-goals, especially warnings or scope exclusions.
- Identify boundary conditions such as required inputs, environment assumptions, permissions, or resource availability.
- Identify misfire risks: cases that look related but should not invoke the skill.
- Assign confidence separately to explicit, semantic, and negative triggers.
- Attach evidence or lower confidence when evidence is weak.
Output Contract
Return activation content suitable for structure_analysis.json:
activation:
explicit_triggers: []
semantic_triggers: []
negative_triggers: []
boundary_conditions: []
misfire_risks: []
confidence:
evidence: []
Anchor-Aware Output
In addition to activation content, emit minimal anchor cards when the source supports them. Keep this lightweight; do not decide dispatch policy inside this skill.
Recommended anchor types:
trigger_anchor: explicit or semantic activation conditions.boundary_anchor: prerequisites, scope limits, and non-goals.handoff_anchor: conditions where another skill or composed anchor should take over.misfire_anchor: false-positive patterns that should not invoke the skill.
Minimal anchor card shape:
anchors:
- id: anchor.<skill_id>.trigger.<slug>
source_skill_id:
anchor_type: trigger_anchor
name:
summary:
evidence:
path:
quote:
confidence: low | medium | high
reuse_modes:
- reference_only
- temporary_composition
- agent_rule_patch
risks:
- possible trigger overlap with existing user skills
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 · 113 lines · 29 tokens per session scan A 80a755bf0666
asa-trigger-boundary-mapper 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 801 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.