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 imMamdouhaboammar/get-fable --skill code-walkthroughgit clone --depth 1 https://github.com/imMamdouhaboammar/get-fableWrote 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/immamdouhaboammar/get-fable/code-walkthrough)<a href="https://agentmods.dev/skills/immamdouhaboammar/get-fable/code-walkthrough"><img src="https://agentmods.dev/badge/skills/immamdouhaboammar/get-fable/code-walkthrough.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.1 | $0.00020 | $0.00587 |
| Opus 5 | $0.00010 | $0.00293 |
| Sonnet 5 | $0.00004 | $0.00117 |
| Haiku 4.5 | $0.00002 | $0.00059 |
Grade A, and why
code-walkthrough 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 7d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: code-walkthrough
description: Generate an interactive walkthrough artifact explaining code in this project — expandable sections, annotated snippets, and "why this matters" callouts, pitched at someone seeing the code for the first time.
No target was given. Ask the user which file, directory, or PR they want explained — one short question — and stop until they answer.
Goal
Produce an interactive explainer artifact for the target above — a
self-contained HTML page a newcomer can read top-to-bottom to understand what
this code does, how it fits together, and why it's built the way it is. Pitch
the writing at explain-like-I'm-new-here: assume the reader is a capable
engineer who has never seen this codebase.
Explore first
Read the target and whatever it immediately depends on (callers, callees,
types it mentions, tests that exercise it). Build a mental model before
writing a word of the artifact. The artifact is only as good as your
understanding.
Structure of the artifact
Write an HTML file and publish it with the Artifact tool. Load
the artifact-design skill first and give the page a
utilitarian treatment — this is a document, not a landing page.
The page should contain, in this order:
- One-paragraph summary — what the target is for, in plain language.
- Map — a short list or simple diagram of the main pieces and how they
connect. For a single file this is the key functions/types; for a
directory it's the files; for a PR it's the before→after. - Walkthrough sections — one
<details>block per piece from the map.
Inside each:- A plain-language explanation of what this piece does.
- An annotated code snippet: the real code (trimmed to the relevant
lines) with inline explanations of the non-obvious parts. - A "why this matters" callout — what would break or be worse if this
piece didn't exist or worked differently.
- Open questions — anything you couldn't determine from the code that a
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.
- 7d ago First seen · 61 lines · 20 tokens per session scan A e543002450e8
code-walkthrough is a skill published in the GitHub repository imMamdouhaboammar/get-fable (3 stars, last pushed 2d ago), licensed MIT. It adds 20 tokens to every session and 587 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
omh-jit-learn
This is a Hermes-native jit-learn workflow skill.
omh-codebase-uml
This is a Hermes-native codebase-uml workflow skill.
guideline-learning-diagnosis
A study aid for learning a medical guideline or its diagnostic criteria. It helps assess what someone knows, find weak sections, and plan further study without diagnosing a real patient.
subscription-setup
A setup workflow for creating recurring medical-learning subscriptions after a doctor’s profile has been registered.
exam-material-recommendation
A study-material recommendation tool for doctors preparing for professional exams or job-related training. It uses the person’s target, timeline, available study time, and specialty, while treating the official exam syllabus as the main reference.
cheatsheet
A Chinese-language reference sheet for AI coding tools such as Claude Code, Cursor, Codex, Copilot, and Aider, covering their uses, commands, and common techniques.