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 agentmods add skills/firou91/dyslex.ai/instruction-decodernpx skills add Firou91/dyslex.ai --skill instruction-decodergit clone --depth 1 https://github.com/Firou91/dyslex.aiWrote 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/firou91/dyslex.ai/instruction-decoder)<a href="https://agentmods.dev/skills/firou91/dyslex.ai/instruction-decoder"><img src="https://agentmods.dev/badge/skills/firou91/dyslex.ai/instruction-decoder.svg" alt="Measured on agentmods" 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 | $0.00042 | $0.00490 |
| Opus 5 | $0.00021 | $0.00245 |
| Sonnet 5 | $0.00008 | $0.00098 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
instruction-decoder 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 today.
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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instruction Decoder
Superpowers Gate
Before applying this skill, verify that Superpowers is available in the current session, such as an active superpowers: skill, using-superpowers, or equivalent Superpowers workflow instructions.
If Superpowers is missing or uncertain, stop and reply exactly with this guidance before doing any dyslex.ai work:
dyslex.ai requires Superpowers before it can run. Install Superpowers from /plugins, or use codex plugin add superpowers@<marketplace> if you manage plugins from the Codex CLI, then start a new session.
Do not perform the requested dyslex.ai workflow until Superpowers is installed and loaded.
Transform a dense instruction into a structure the user can verify.
Functional Mechanism
Primary dimensions: workingMemory.multiStepInstructionLoad, workingMemory.simultaneousInformationLoad, executiveFunction.sequencingLoad, executiveFunction.planningLoad, and language.discourseOrganizationLoad.
Decode instructions by externalizing the structure that would otherwise need to be held in working memory.
Interaction Risk
Dense prompts can mix goal, constraints, warnings, order, forbidden actions, and success criteria. The user or agent may miss one part or act in the wrong order.
Agent Strategy
- Extract the requested result first.
- Separate constraints from steps and success criteria.
- Preserve exact technical tokens.
- Ask only about ambiguities that materially change the result.
- Use the smallest confirmation needed when intent is likely but not certain.
Avoid
- Do not add requirements not present in the source.
- Do not infer a diagnosis from disordered or dense instructions.
- Do not turn every typo into a clarification question.
- Do not collapse constraints into generic summary text.
Output Format
Use this structure:
Result requested
What is provided
Constraints
Steps
Do not do
Success criteria
Rules
- Keep the original intent.
- Separate facts from assumptions.
- Use exact names for files, functions, commands, and concepts.
- Do not add requirements not present in the source text.
- Ask only about ambiguities that materially affect the result.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed · +25 lines 1b95a522262a
- 4d ago First seen · 42 lines · 42 tokens per session scan A 096e0f34e707
instruction-decoder is a skill published in the GitHub repository Firou91/dyslex.ai (7 stars, last pushed 2d ago), licensed Apache-2.0. It adds 42 tokens to every session and 490 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…