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 jmcentire/kindex --skill kindex-learngit clone --depth 1 https://github.com/jmcentire/kindexWrote 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/jmcentire/kindex/kindex-learn)<a href="https://agentmods.dev/skills/jmcentire/kindex/kindex-learn"><img src="https://agentmods.dev/badge/skills/jmcentire/kindex/kindex-learn/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/jmcentire/kindex/kindex-learn"><img src="https://agentmods.dev/badge/skills/jmcentire/kindex/kindex-learn.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00035 | $0.00188 |
| Opus 5 | $0.00017 | $0.00094 |
| Sonnet 5 | $0.00007 | $0.00038 |
| Haiku 4.5 | $0.00003 | $0.00019 |
Grade A, and why
kindex-learn 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 9d 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
Kindex Learn
Extract knowledge from the current conversation and add it to the graph.
Instructions
- Summarize the key discoveries, decisions, and concepts from this session in 2-3 paragraphs
- Call the
learnMCP tool with this summary text - If specific decisions were made, call
addfor each one withnode_type: "decision" - If new connections between existing concepts were discovered, call
linkto create edges - Report what was captured: number of new nodes, links, and any bridge suggestions
Focus on what matters — not every line of code, but the insights, patterns, and decisions that would help a future session.
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.
- 9d ago First seen · 19 lines · 35 tokens per session scan A 88b43c8f8549
kindex-learn is a skill published in the GitHub repository jmcentire/kindex (26 stars, last pushed 6d ago), licensed MIT. It adds 35 tokens to every session and 188 once invoked, about $0.0002 per session on Opus 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
kn-implement
Use when implementing a task - follow the plan, check ACs, track progress.
kn-spec
Use when creating a specification document for a feature (SDD workflow).
kn-flow
Use when orchestrating a full Knowns spec or task wave through planning, implementation, review, integration, and verification, optionally using sub-agents when scopes are parallel-safe.
kn-handoff
Use when a feature crosses repository boundaries and one side must hand work to the other - generates a self-contained frontend-to-backend brief or backend-to-frontend API contract.
kn-debug
Use when debugging errors, test failures, build issues, or blocked tasks — structured triage to fix to learn.
kn-plan
Use when creating an implementation plan for a task.