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 harnessprotocol/harness-kit --skill explaingit clone --depth 1 https://github.com/harnessprotocol/harness-kitWrote 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/harnessprotocol/harness-kit/explain)<a href="https://agentmods.dev/skills/harnessprotocol/harness-kit/explain"><img src="https://agentmods.dev/badge/skills/harnessprotocol/harness-kit/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/harnessprotocol/harness-kit/explain"><img src="https://agentmods.dev/badge/skills/harnessprotocol/harness-kit/explain.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 160 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
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.00095 | $0.02215 |
| Opus 5.5 | $0.00038 | $0.00886 |
| Sonnet 5.5 | $0.00019 | $0.00443 |
| Haiku 4.5 | $0.00010 | $0.00221 |
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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Structured Code Explainer
Overview
Produce layered explanations of code — files, directories, functions, classes, or cross-cutting concepts. Designed for developers working in unfamiliar parts of a codebase.
Core principles:
- Adaptive depth. A single function gets a focused deep-dive. A directory gets a map first, then the user picks where to zoom.
- Project-aware. If the project has a CLAUDE.md, reference its Architecture section to ground explanations in the project's own terminology.
- Conversation output. Explanations go to the conversation, not files. The user can ask to save if they want.
When to Use
User types /explain followed by:
- File path → explain that file
- Directory path → map the directory structure, then explain key components
- Function or class name → find the definition, explain it in context
- Natural language concept → search the codebase for relevant files and explain the concept/flow
Invocation Examples
/explain src/auth/middleware.ts
/explain the payment processing flow
/explain src/services/
/explain OrderProcessor.process
/explain how webhooks get dispatched
Workflow Order (MANDATORY)
You MUST follow this order. No skipping steps.
Step 1: Parse Input
Classify the argument:
| Type | Detection | Example |
|---|---|---|
| File path | Has file extension or resolves to a file | src/auth/middleware.ts |
| Directory path | Resolves to a directory (or ends with /) |
src/services/ |
| Symbol name | Looks like a function, class, or method (CamelCase, dot notation, ::) |
OrderProcessor.process |
| Concept | Natural language, doesn't resolve to a file or directory | the payment processing flow |
If ambiguous (e.g., auth could be a directory or a concept), check the filesystem first. If it resolves to a file or directory, treat it as that. Otherwise, treat it as a concept.
Step 2: Gather Context
For a file path:
- Read the target file
- Identify imports/dependencies — read the most important ones (up to 5 files)
- Search for callers — search for the filename or its key exports across source files in the codebase (filter to relevant file types like
*.ts,*.py,*.go, etc. to avoid noise from docs, tests, and build output) - Limit total files read to ~10 to stay focused
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.
- 1mo ago First seen · 219 lines · 95 tokens per session scan A c2bf0b98b232
explain is a skill published in the GitHub repository harnessprotocol/harness-kit (10 stars, last pushed today), licensed Apache-2.0. It adds 95 tokens to every session and 2,215 once invoked, about $0.0004 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
learn-from-fix
Capture Elixir/Ecto/LiveView lessons and Hex API rules. Use after corrections or when asked to document learning, record a lesson, prevent a fixed mistake, or remember package guidance with --library.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
examples
Provide Phoenix, LiveView, Ecto, OTP, or Oban examples. Use when asked for sample code, a walkthrough, a proper implementation, or expected workflow output. Pair with domain skills. NOT for debugging, direct changes, best-practice advice, or audits.
learn
Guided, hands-on course teaching architects how to use Codex or Claude Code — six short modules, each built around an exercise on a bundled sandbox project (a fictional Brooklyn art museum expansion). Resumable across sessions via PROGRESS.md. Use when the user runs $learn or /as:learn, says they're new to AI-assisted…
intro
Walk through the Elixir/Phoenix plugin commands, workflow, and features in 6 interactive sections. Use when a new user wants to learn what the plugin offers or needs a refresher on available commands.
architecture-knowledge
Explain US architecture professional-practice terms, phases, deliverables, roles, delivery methods, AIA contract families, CSI documentation systems, or NCS at a high level. Use for questions such as “what is a CD set?” or “what does 50% CDs mean?”; do not use for code/jurisdiction, outline-spec, agreement-scope, or…