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-resource-role-analyzergit 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-resource-role-analyzer)<a href="https://agentmods.dev/skills/3yesore/letuenforskills/asa-resource-role-analyzer"><img src="https://agentmods.dev/badge/skills/3yesore/letuenforskills/asa-resource-role-analyzer/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-resource-role-analyzer"><img src="https://agentmods.dev/badge/skills/3yesore/letuenforskills/asa-resource-role-analyzer.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.00027 | $0.00953 |
| Opus 5 | $0.00014 | $0.00477 |
| Sonnet 5 | $0.00005 | $0.00191 |
| Haiku 4.5 | $0.00003 | $0.00095 |
Grade A, and why
asa-resource-role-analyzer 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ASA Resource Role Analyzer
Use this internal meta-skill when a model must explain what each important file or resource does in a skill package.
This skill fixes the failure mode where analysis lists files but does not explain whether they are instructions, templates, executable tools, references, examples, assets, tests, configs, schemas, or compliance material.
Inputs
- Deterministic file inventory for one skill package.
SKILL.mdcontent and package layout.- Related files under
scripts,references,assets,examples,templates,tests, and root files. - Dependency index when available.
Process
- Classify each important resource by role.
- Determine whether the resource is must-read, on-demand, optional, or ignorable for execution.
- Map the resource to a workflow stage: activation, planning, context loading, execution, validation, delivery, learning, or compliance.
- Identify reuse value: high, medium, low, or unknown.
- Identify risk or brittleness, such as missing dependencies, external services, large context, or license constraints.
- Distinguish execution resources from learning/reference resources.
- Attach evidence from file layout, names, source text, or dependency extraction.
Output Contract
Return resource role content suitable for structure_analysis.json:
resource_roles:
- path:
role:
stage:
read_policy: must_read | on_demand | optional | ignore
reuse_value: high | medium | low | unknown
risk:
evidence: []
Anchor-Aware Output
In addition to resource role content, emit minimal anchor cards for resources that may affect reuse or composition. Keep this lightweight; do not copy files or decide whether to apply them to a user project.
Recommended anchor types:
resource_anchor: an important file, directory, reference, asset, or config.template_anchor: a reusable scaffold, prompt template, UI template, document template, or schema.tool_anchor: a script, command, API helper, or executable utility.dependency_anchor: package, runtime, environment variable, service, or external requirement.portable_resource_anchor: a resource that can be copied or adapted safely.non_portable_resource_anchor: a resource that should stay reference-only or requires permission/adaptation.
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 · 118 lines · 27 tokens per session scan A 312044fe30ca
asa-resource-role-analyzer is a skill published in the GitHub repository 3yesore/LetUenforskills (2 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 953 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.