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-workflow-trace-buildergit 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-workflow-trace-builder)<a href="https://agentmods.dev/skills/3yesore/letuenforskills/asa-workflow-trace-builder"><img src="https://agentmods.dev/badge/skills/3yesore/letuenforskills/asa-workflow-trace-builder/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-workflow-trace-builder"><img src="https://agentmods.dev/badge/skills/3yesore/letuenforskills/asa-workflow-trace-builder.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.00028 | $0.01054 |
| Opus 5 | $0.00014 | $0.00527 |
| Sonnet 5 | $0.00006 | $0.00211 |
| Haiku 4.5 | $0.00003 | $0.00105 |
Grade B, and why
asa-workflow-trace-builder scanned grade B with 1 finding 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 10d 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
- `SKILL.md` ordered steps, headings, rules, warnings, and output instructions. How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ASA Workflow Trace Builder
Use this internal meta-skill when a model must reconstruct a skill workflow from user request to final delivery.
This skill fixes the failure mode where workflow analysis becomes a vague list of actions without inputs, outputs, resource usage, actor responsibility, evidence, or reusable workflow anchors.
Inputs
- Structure analysis for one skill package.
SKILL.mdordered steps, headings, rules, warnings, and output instructions.- Resource role analysis when available.
- Source snapshot and evidence blocks.
Process
- Start from the user intent or task trigger.
- Identify each step in execution order.
- For every step, state input, action, output, actor, resources, confidence, and whether it is inferred.
- Map how each step enables the next step.
- Extract workflow anchors from reusable step chains, handoffs, replaceable steps, validation gates, and output transitions.
- Extract decision points, verification points, failure modes, recovery paths, and stop conditions.
- Separate model actions from script/tool/human/external actions.
- Build a short pipeline for visual reports and a full step list for detailed reports.
- Attach evidence to every high-confidence step and every proposed anchor.
Output Contract
Return workflow trace content suitable for workflow_analysis.json:
workflow_trace:
summary:
zh:
en:
pipeline: []
steps:
- id:
name:
zh:
en:
input:
action:
output:
actor: model | script | human | external_tool | unknown
resources: []
downstream:
confidence: high | medium | low | unknown
inferred: true | false
evidence: []
decision_points: []
verification_points: []
failure_modes: []
anchors:
workflow_anchor:
- id:
name:
description:
source_steps: []
reusable_as: prompt_patch | checklist | mini_skill | workflow_module | reference_pattern
required_inputs: []
produced_outputs: []
dependencies: []
confidence: high | medium | low | unknown
evidence: []
handoff_anchor:
- id:
from_step:
to_step:
handoff_object:
contract:
failure_if_missing:
confidence: high | medium | low | unknown
evidence: []
replaceable_step_anchor:
- id:
step_id:
replace_with:
safe_when:
unsafe_when:
user_control: keep_original | choose_alternative | remove | defer
confidence: high | medium | low | unknown
evidence: []
validation_step_anchor:
- id:
step_id:
validation_target:
pass_signal:
fail_signal:
repair_action:
confidence: high | medium | low | unknown
evidence: []
output_transition_anchor:
- id:
from_output:
to_surface:
transformation:
preserves: []
risks: []
confidence: high | medium | low | unknown
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.
- 10d ago First seen · 148 lines · 28 tokens per session scan B 117feb51dada
asa-workflow-trace-builder is a skill published in the GitHub repository 3yesore/LetUenforskills (2 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 1,054 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). 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.