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-reader-layer-writergit 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-reader-layer-writer)<a href="https://agentmods.dev/skills/3yesore/letuenforskills/asa-reader-layer-writer"><img src="https://agentmods.dev/badge/skills/3yesore/letuenforskills/asa-reader-layer-writer/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-reader-layer-writer"><img src="https://agentmods.dev/badge/skills/3yesore/letuenforskills/asa-reader-layer-writer.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.00827 |
| Opus 5 | $0.00014 | $0.00413 |
| Sonnet 5 | $0.00005 | $0.00165 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade A, and why
asa-reader-layer-writer 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 12d 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 Reader Layer Writer
Use this internal meta-skill when structured decomposition must become a readable report, Obsidian note, tutorial, or visual surface.
This skill fixes the failure mode where reports repeat the same summary, assume too much skill-design knowledge, bury implementation details without a reading path, or fail to expose reusable anchor cards for learning and operation.
Inputs
- Inventory, structure analysis, workflow analysis, reviewer output, and patterns.
- Reader intent: beginner learning, expert implementation, reuse, comparison, or audit.
- Available surfaces: web report, cinema narrative, Obsidian vault, graph, and data files.
Process
- Start with a reader guide that explains how to read the report.
- Write a beginner layer that explains concepts without jargon.
- Write an expert layer that preserves implementation details, constraints, and evidence.
- Put identity, trigger, workflow, resources, evidence, and reuse in a clear order.
- Avoid repeating the same sentence in hero, snapshot, manual, and appendix.
- Explain specialized terms such as trigger, boundary, context, evidence, and workflow.
- Convert key concepts, learning notes, and operational guidance into reader anchors.
- Keep Chinese as the default layer when project language is bilingual.
- Preserve bilingual structure so English can mirror the same meaning.
Output Contract
Return reader-layer guidance suitable for report and vault exporters:
reader_layers:
beginner:
expert:
glossary: []
reading_order: []
report_notes: []
obsidian_notes: []
anchors:
anchor_card:
- id:
source_anchor_id:
title:
zh:
en:
one_sentence:
zh:
en:
why_it_matters:
zh:
en:
reader_level: beginner | intermediate | expert | operator
source_section:
evidence: []
learning_note_anchor:
- id:
topic:
explains:
zh:
en:
prerequisites: []
examples: []
common_misreadings: []
obsidian_links: []
evidence: []
operator_guide_anchor:
- id:
task:
when_to_use:
steps: []
expected_inputs: []
expected_outputs: []
safety_checks: []
reuse_modes: []
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.
- 12d ago First seen · 118 lines · 27 tokens per session scan A dac1e891107c
asa-reader-layer-writer 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 827 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
transformer-attention
Use when reasoning about Transformer self-attention, multi-head attention, positional encoding, masked decoder attention, or why attention replaced recurrence/convolutions in sequence models; not for generic NLP or unrelated attention topics.
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.
lookup-topic
Look up a help topic with progressive depth. First call returns concept, repeat calls escalate to task then reference. Triggers on: look up topic, open template, tell me more, go deeper, start over.