Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Kanevry/session-orchestratornpx agentmods add skills/kanevry/session-orchestrator/eli5Wrote 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/kanevry/session-orchestrator/eli5)<a href="https://agentmods.dev/skills/kanevry/session-orchestrator/eli5"><img src="https://agentmods.dev/badge/skills/kanevry/session-orchestrator/eli5/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/kanevry/session-orchestrator/eli5"><img src="https://agentmods.dev/badge/skills/kanevry/session-orchestrator/eli5.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
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 →
- medium Agent Snooping · line 9 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 13 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00066 | $0.00380 |
| Opus 5.5 | $0.00026 | $0.00152 |
| Sonnet 5.5 | $0.00013 | $0.00076 |
| Haiku 4.5 | $0.00007 | $0.00038 |
Grade A, and why
eli5 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
eli5
Portable mirror — generated, do not edit. The canonical workflow lives at
skills/eli5/SKILL.md; read that file for the full instructions. This mirror carries only agentskills.io-spec-legal frontmatter so harnesses that discover skills under.agents/skills/can find and route to the skill.Regenerate with
node scripts/generate-agents-skills.mjs.
Read the linked document in full and follow its complete workflow, including prechecks and stop conditions. Resolve its link relative to this SKILL.md, not the project working directory. The plugin root is three directories above this file. Resolve package paths such as skills/ and scripts/ from that root and relative links in the canonical document from its own directory. Keep the user’s project as the target of project operations.
$ARGUMENTS means the trailing user input after the selected command skill, or an empty string when absent. Preserve flags, quoted text, and Unicode as data. Do not perform global substitution in the command document, shell expansion on the argument string, or execution of that string as shell code. Pass command arguments through structured tool parameters or safely quoted individual arguments.
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 Changed · +4 lines 10cea8f76ecb
- 1mo ago Changed · +2 lines c3045f99cd0a
- 1mo ago Changed · +7 lines f5fc7285199d
- 1mo ago First seen · 14 lines · 66 tokens per session scan A 78862a45d81b
eli5 is a skill published in the GitHub repository Kanevry/session-orchestrator (52 stars, last pushed today), licensed MIT. It adds 66 tokens to every session and 380 once invoked, about $0.0003 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
learn
Knowledge compiler. Extracts patterns, decisions, and anti-patterns from completed campaigns and evolve cycles, then compiles them into structured wiki pages that integrate with existing knowledge rather than appending isolated files. Implements flush→compile→lint pipeline. Auto-triggered by /postmortem and /evolve…
ai-literacy-assessment
This skill should be used when the user asks to "assess AI literacy", "run an assessment", "check literacy level", "evaluate our AI collaboration", "where are we on the framework", or wants to determine their team's AI literacy level using the ALCI instrument.
literacy-improvements
Use when generating a prioritised improvement plan after an AI literacy assessment, or when a user knows their current level and wants to know what to do next — maps gaps to specific plugin commands and skills, grouped by target level, with accept/skip/defer for each item.
literate-programming
Use when creating new source files, writing new functions or types, or significantly rewriting existing code — ensures code is structured for humans to read first, with narrative preambles, reasoning-based documentation, and presentation ordered by understanding rather than compiler convention.
harness-engineering
This skill should be used when the user asks about "harness engineering", "what is a harness", "harness framework", "AI code quality", "context engineering", "architectural constraints", "garbage collection for code", or wants to understand the conceptual foundation behind the harness-engineering plugin.
harness-onboarding
Use when generating a human-readable onboarding document from HARNESS.md, AGENTS.md, and REFLECTIONLOG.md — produces a friendly guide for new team members joining a harnessed project.