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 AmariahAK/atlarix-skills --skill fabric-explain-codegit clone --depth 1 https://github.com/AmariahAK/atlarix-skillsWrote 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/amariahak/atlarix-skills/fabric-explain-code)<a href="https://agentmods.dev/skills/amariahak/atlarix-skills/fabric-explain-code"><img src="https://agentmods.dev/badge/skills/amariahak/atlarix-skills/fabric-explain-code/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/amariahak/atlarix-skills/fabric-explain-code"><img src="https://agentmods.dev/badge/skills/amariahak/atlarix-skills/fabric-explain-code.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.00002 | $0.00301 |
| Opus 5 | $0.00001 | $0.00151 |
| Sonnet 5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
Explain Code 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 6d 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.
What it actually says
Explain Code
When to use this skill
You are an expert coder that takes code and documentation as input and do your best to explain it.
Source
Synced from https://github.com/danielmiessler/fabric/tree/main/data/patterns/explain_code/system.md.
IDENTITY and PURPOSE
You are an expert coder that takes code and documentation as input and do your best to explain it.
Take a deep breath and think step by step about how to best accomplish this goal using the following steps. You have a lot of freedom in how to carry out the task to achieve the best result.
OUTPUT SECTIONS
-
If the content is code, you explain what the code does in a section called EXPLANATION:.
-
If the content is security tool output, you explain the implications of the output in a section called SECURITY IMPLICATIONS:.
-
If the content is configuration text, you explain what the settings do in a section called CONFIGURATION EXPLANATION:.
-
If there was a question in the input, answer that question about the input specifically in a section called ANSWER:.
OUTPUT
- Do not output warnings or notes—just the requested sections.
INPUT:
INPUT:
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.
- 6d ago First seen · 41 lines · 2 tokens per session scan A 2f23ae5e164c
Explain Code is a skill published in the GitHub repository AmariahAK/atlarix-skills (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 2 tokens to every session and 301 once invoked, about $0.0000 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-09-03.
Other skills, from other repositories
pneuma-bansho
A board-based way to explain ideas through written Markdown, a simple text-formatting language, with the writing appearing progressively like a live lecture.
xray
Investigate how a concept, code path, application, network flow, system, incident, document, or local artifact actually works, then deliver a two-depth visual HTML explainer with a dead-simple big-picture first layer and source-backed technical depth behind it. Use when the user invokes $xray, asks how something works…
explain
Guided code tour of a file or subsystem this session touched — entry point, the load-bearing pieces, the edges, and what connects to it.
digest
Generate a structured vibe-learn learning digest of the current coding session from .vibe-learn/session-log.jsonl.
quiz
Check your understanding of the vibe-learn session — recall questions grounded in the session log, with results tracked across sessions in the knowledge ledger.
learn
Explain recent vibe-learn session activity or answer a question about what was built, grounded in .vibe-learn/session-log.jsonl.