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/samibs/skillfoundry/explainnpx skills add samibs/skillfoundry --skill explaingit clone --depth 1 https://github.com/samibs/skillfoundryWhat 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.00009 | $0.04694 |
| Opus 5 | $0.00005 | $0.02347 |
| Sonnet 5 | $0.00002 | $0.00939 |
| Haiku 4.5 | $0.00001 | $0.00469 |
Grade A, and why
explain scanned grade A 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- smoke-test.sh uses curl with no auth (acceptable for health endpoint) How it starts
The opening of the file, as written. The whole thing — 534 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/explain - Execution Explainer
Reconstruct, trace, and explain the last agent action in plain English. Three levels of detail: quick, verbose, and story-level. No mystery, no ambiguity -- just cold facts about what happened and why.
Usage
/explain Explain the last agent action (quick mode)
/explain --verbose Full trace with file changes and decision rationale
/explain --story STORY-XXX All actions for a story in chronological order
/explain --agent <name> Last action by a specific agent
/explain --session <id> All actions from a specific session
/explain --diff Include before/after file diffs in output
Instructions
You are the Execution Explainer -- the forensic analyst of agent activity. When a developer asks "what just happened?", you reconstruct the full trace from scattered logs, dispatch state, and git history. You never speculate. If the data is incomplete, you say so.
Core Principle: Every agent action leaves traces. Find them, connect them, explain them.
PHASE 1: CONTEXT GATHERING
Where to Look
Agent activity leaves traces in multiple locations. Search all of them, in this order:
| Source | Path | Contains |
|---|---|---|
| Swarm task queue | .claude/swarm/task-queue.jsonl |
Completed and pending swarm tasks with agent assignments |
| Dispatch state | .claude/dispatch-state.json |
Wave dispatch records: which agents ran, in what order, outcomes |
| Remediation logs | logs/remediations.md |
Auto-fix actions taken by fixer or debugger |
| Escalation logs | logs/escalations.md |
Points where agents escalated to the user or another agent |
| Git log | git log --oneline -20 |
Recent commits with agent attribution in commit messages |
| Scratchpad | .claude/scratchpad.md |
Agent notes, intermediate decisions, handoff context |
| Agent stats | memory_bank/knowledge/agent-stats.jsonl |
Event log with durations, outcomes, error types |
| Memory bank | memory_bank/knowledge/decisions-universal.jsonl |
Decisions recorded during execution |
| Error log | memory_bank/knowledge/errors-universal.jsonl |
Errors encountered and how they were handled |
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.
- 2d ago First seen · 534 lines · 9 tokens per session scan A 77c35d0fe559
explain is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 4,694 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.
ring:applying-composition-patterns
React composition patterns that scale. Avoid boolean prop proliferation by using compound components, lifting state, and composing internals. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or during architecture review. Skip for simple components with 1-2 props…
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…
ring:exploring-codebases
Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…
ring:auditing-dependency-security
Auditing a dependency for supply-chain risk before install (pip/npm/go/cargo): checks typosquatting, maintainer/age risk, vulnerability DBs (OSV, GHSA, Socket), and lockfile hash pinning, then emits a risk score and approve/conditional/escalate/block decision. Use when adding or updating a dependency, reviewing a…