Skills-Agent: Skill for Claude Code

.agents/skills/explain/SKILL.md

explain is a skill for Claude Code, Codex from VoTruongDanh/Skills-Agent. It costs 62 tokens per session (982 once invoked), scanned A, original, MIT.

A skill for explaining code, logic, and software architecture in plain language. It can tailor explanations to backend, interface, database, security, or documentation topics.

In plain words
What is it for?
For high-level explanations, step-by-step logic walkthroughs, architecture discussions, and explanations of backend, interface, database, or security code.
Why use it?
It gives an agent a structured way to understand the requested code and project context before explaining it.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is VoTruongDanh/Skills-Agent's own configuration. It tells Claude Code and Codex how to work on Skills-Agent itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Skills-Agent configures →

Reuse

Borrowing it

Nothing to install: this file belongs to VoTruongDanh/Skills-Agent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/VoTruongDanh/Skills-Agent/main/.agents/skills/explain/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/VoTruongDanh/Skills-Agent

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for explain

README.md
[![agentmods](https://agentmods.dev/badge/skills/votruongdanh/skills-agent/explain/github.svg)](https://agentmods.dev/skills/votruongdanh/skills-agent/explain)
Your own site
<a href="https://agentmods.dev/skills/votruongdanh/skills-agent/explain"><img src="https://agentmods.dev/badge/skills/votruongdanh/skills-agent/explain/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.

agentmods 80×15 button for explain

Your own site · 80×15
<a href="https://agentmods.dev/skills/votruongdanh/skills-agent/explain"><img src="https://agentmods.dev/badge/skills/votruongdanh/skills-agent/explain.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 982 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00062 $0.00982
Opus 5 $0.00031 $0.00491
Sonnet 5 $0.00012 $0.00196
Haiku 4.5 $0.00006 $0.00098

Measured 9d ago against content hash 6e3a71c0b5fe, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

explain 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 9d 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.

.agents/skills/explain/SKILL.md · 75 lines

How it starts

The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Memory Protocol

START: Read .ai-memory.md from project root. Check tech stack, architecture notes, past explanations, and domain context. END: Update .ai-memory.md using Memory Compaction Rules with: what was explained, key insights, misconceptions clarified, and follow-ups.

Goal

Help the user deeply understand code, logic, architecture, or behavior — at the level of detail they need.

Agent Routing

  • If explaining backend/API logic → read .kiro/skills/agents/agents/backend-specialist.md and apply its knowledge
  • If explaining UI/component behavior → read .kiro/skills/agents/agents/frontend-specialist.md and apply its knowledge
  • If explaining database schema/queries → read .kiro/skills/agents/agents/database-architect.md and apply its knowledge
  • If explaining security mechanisms → read .kiro/skills/agents/agents/security-auditor.md and apply its knowledge
  • Default → read .kiro/skills/agents/agents/documentation-writer.md for clear, structured explanation

Socratic Gate

Before explaining, verify:

  1. Which file, function, or code block should be explained?
  2. What level of detail? (high-level overview vs line-by-line walkthrough)
  3. What is the user's familiarity level with this area? If any answer is unclear, ASK before proceeding.

Workflow

  1. Read Memory — Load .ai-memory.md for project context, tech stack, and architecture.
  2. Read the target code thoroughly — understand intent, not just syntax.
  3. Identify the explanation scope: single function, module, data flow, or architecture.
  4. Explain at the requested level:
    • High-level: Purpose, inputs/outputs, how it fits in the system.
    • Detailed: Step-by-step logic, control flow, edge cases, design decisions.
    • Line-by-line: What each line does and why.
  5. Highlight non-obvious logic, hidden side effects, and design trade-offs.
  6. Use analogies or diagrams if the concept is complex.
  7. Suggest follow-up topics if relevant (e.g., "you may also want to understand X").
  8. Quality Gate — Read .kiro/skills/_scripts/checklist.md for cross-cutting checks.
  9. Update Memory — Save explanation context and insights to .ai-memory.md.

Read the full file on GitHub · 75 lines

Changes

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.

  1. 9d ago First seen · 75 lines · 62 tokens per session scan A 6e3a71c0b5fe

Subscribe to this mod's changes

explain is a skill published in the GitHub repository VoTruongDanh/Skills-Agent (2 stars, last pushed 4d ago), licensed MIT. It adds 62 tokens to every session and 982 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

hr-onboarding

A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".

nexu-io/open-design · 62 tokens

book-mirror

Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…

garrytan/gbrain · 138 tokens

miniapp

Build a tiny interactive HTML playground only when someone asks to see, play with, or step through a mechanism.

yc-software/qm · 25 tokens

eli5

Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.

companion-inc/feynman · 63 tokens

deck-course-module

A course or workshop slide template with persistent learning goals, teaching pages, multiple-choice self-tests, and a wrap-up.

nexu-io/html-anything · 25 tokens

master-yinguang

A reference-based assistant for questions about Yinguang and Pure Land Buddhism, a Buddhist tradition focused on faith, ethical living, and practice connected with rebirth in the Pure Land. It can answer in Yinguang’s historical teaching style.

xr843/Master-skill · 274 tokens