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 ramboz/jig --skill explaingit clone --depth 1 https://github.com/ramboz/jigWrote 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/ramboz/jig/explain)<a href="https://agentmods.dev/skills/ramboz/jig/explain"><img src="https://agentmods.dev/badge/skills/ramboz/jig/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.
<a href="https://agentmods.dev/skills/ramboz/jig/explain"><img src="https://agentmods.dev/badge/skills/ramboz/jig/explain.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00173 | $0.05020 |
| Opus 5.5 | $0.00069 | $0.02008 |
| Sonnet 5.5 | $0.00035 | $0.01004 |
| Haiku 4.5 | $0.00017 | $0.00502 |
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 1mo 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 — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec 065 introduces this skill as jig's on-demand explainer — the third consumer of the shipped lexicon (065-01). The barrier jig is lowering is vocabulary: the artifacts are dense with opinionated jargon (SPIDR, ADR, vertical slice, reconciliation, deviation log, DoR/AC/DoD, frontmatter) and almost none of it is explained where the reader meets it. The hook (065-02) surfaces one-line defs just-in-time; this skill is the strong-handholding escalation — define a term in depth, or translate a whole dense spec/ADR into plain language for a junior.
Like
/jig:clarify,/jig:pr-review, and/jig:arch-review, explain is a judgment skill — it ships no.pyhelper. The only determinism it needs (load the merged lexicon, read the named artifact, resolve the refs it links) Claude runs inline via Read + the 065-01 loader. The plain-language quality is judgment exercised by this prompt, not something a unit test can assert — the same accepted shape as every judgment-only jig skill.
What this skill does
Translates jig's vocabulary and artifacts into plain language for a reader who is new here — a junior, or anyone meeting spec-driven work for the first time. It has three modes, selected by what the argument is:
- Term mode — the argument is a word or short phrase (
/jig:explain reconciliation). The skill returns that term's plain-language definition from the merged lexicon (jig's shippedlexicon.jsonwith the project'sdocs/memory/glossary.mdoverlaid on top — 065-01), plus its example and see-also when present. If the term is not in the lexicon, the skill says so plainly rather than inventing a definition. - Artifact mode — the argument is a path to a spec or ADR
(
/jig:explain docs/specs/062-refactor-workflow/spec.md). The skill produces a fixed-shape, junior-grade walkthrough of that artifact, defining every jig term it uses inline and auto-pulling the ADRs/specs it links so the reader doesn't have to chase references. - Passage mode — the argument is a pasted snippet of jig output that is
neither a single term nor a file path: a review
VERDICT:envelope, a status-board row likeIN_PROGRESS (wt-me), a hook's "Unrecognized references in prompt…" message, aworkflow.pytransition refusal, asession-planblock. The skill scans the snippet for jig terms (defining each inline) and explains what it is and what — if anything — the reader should do. When the snippet carries no jig vocabulary at all, it gives a plain generic read. This is the mode for the most common confusion moment: a reader pastes the thing that stumped them.
All three modes are ephemeral: the output is chat-only. The skill writes nothing
to disk — no --save flag, no appended section, no file mutation. This keeps
the hot path clean (the 055/057 context-cost discipline) and matches the
clarify-Q3 resolution that explain output is always chat-only.
This is a best-effort comprehension floor, not a guarantee the reader will understand everything — the same honest framing as jig's security floor (ADR-0013) and the soft context mechanisms (055/057). The skill surfaces and explains; it does not certify understanding.
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.
- 1mo ago First seen · 350 lines · 173 tokens per session scan A b62b9f0235bf
explain is a skill published in the GitHub repository ramboz/jig (7 stars, last pushed 3d ago), licensed MIT. It adds 173 tokens to every session and 5,020 once invoked, about $0.0007 per session on Opus 5.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
onboarding
Skill "onboarding" from knitli/toolshed, covering codeweaver first-run onboarding, your goal, setup flow, 1. welcome & overview and 2. embedding provider selection.
setup
Skill "setup" from knitli/toolshed, covering codeweaver setup / reconfiguration, your goal, setup flow, 1. welcome & context and 2. embedding provider selection.
.codex
Skill ".codex" from knitli/toolshed, covering context hygiene skill, name, description, instructions and 1. discovery.
gh-stack
Manage stacked branches and pull requests with the gh-stack GitHub CLI extension. Use when the user wants to create, push, rebase, sync, navigate, or view stacks of dependent PRs. Triggers on tasks involving stacked diffs, dependent pull requests, branch chains, or incremental code review workflows.
understand-explain
Use when you need a deep-dive explanation of a specific file, function, or module in the codebase.
baoyu-comic
A tool for creating original educational comics that explain knowledge or ideas through multiple illustrated panels. It supports different art styles and tones and can create several comics in one batch.