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 pilinux/gorest --skill explain-codegit clone --depth 1 https://github.com/pilinux/gorestWrote 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/pilinux/gorest/explain-code)<a href="https://agentmods.dev/skills/pilinux/gorest/explain-code"><img src="https://agentmods.dev/badge/skills/pilinux/gorest/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/pilinux/gorest/explain-code"><img src="https://agentmods.dev/badge/skills/pilinux/gorest/explain-code.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.00023 | $0.00236 |
| Opus 5.5 | $0.00009 | $0.00094 |
| Sonnet 5.5 | $0.00005 | $0.00047 |
| Haiku 4.5 | $0.00002 | $0.00024 |
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 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.
What it actually says
Explain Code
When to Use
- The user asks "how does X work?" or needs a human-readable overview tied to exact code locations.
Rules
- Read-only and source-cited: every non-trivial claim must include
path:line. - Keep summaries short and pragmatic. Focus on inputs/outputs, side effects, and error handling.
Output
- What it does: 1-4 sentences.
- How it works: 3-6 bullets with
path:linecitations for key statements. - Key types/APIs: short list with
path:line. - Edge cases / invariants: 1-3 bullets.
Examples
- "Explain
handler.Loginbehavior and where passwords are hashed." - "How does the JWT blacklist work end-to-end?"
Related Skills
file-reader(low-level excerpts),code-navigation(impact mapping)
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 · 36 lines · 23 tokens per session scan A 30f49dcbcf28
explain-code is a skill published in the GitHub repository pilinux/gorest (506 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 236 once invoked, about $0.0001 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-30.
Other skills, from other repositories
golang
Use when building Go backend services, implementing goroutines/channels, handling errors idiomatically, writing tests with testify, or following Go best practices for APIs/CLI tools.
golang-backend-development
Complete guide for Go backend development including concurrency patterns, web servers, database integration, microservices, and production deployment.
software-engineer-go
Use when implementing or modifying Go applications, services, modules, or tests.
use-modern-go
Use the Modern Go Guidelines CLI whenever writing, modifying, fixing, or refactoring Go code. Apply its version-specific guidance to generated changes.
migrate-goldmark-extension-v1-to-v2
Migrate goldmark extension from goldmark v1 to v2.
pi-loop-forensics
Diagnose pi-go agent loops and degenerate turns — "agent loop aborted", runaway thinking with no tool calls, repeated phrases. Discriminates genuine model repetition collapse from a race, a tool-parse failure, or a too-low guard, and A/B replays a seed session across providers.