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-capturegit 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-capture)<a href="https://agentmods.dev/skills/jmcentire/kindex/kindex-capture"><img src="https://agentmods.dev/badge/skills/jmcentire/kindex/kindex-capture/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-capture"><img src="https://agentmods.dev/badge/skills/jmcentire/kindex/kindex-capture.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.00045 | $0.00228 |
| Opus 5 | $0.00023 | $0.00114 |
| Sonnet 5 | $0.00009 | $0.00046 |
| Haiku 4.5 | $0.00005 | $0.00023 |
Grade A, and why
kindex-capture 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 10d 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 Capture
Capture a specific piece of knowledge, constraint, or decision right now.
Instructions
- Identify what the user wants to capture
- Determine the appropriate node type:
concept— general knowledge or insightdecision— a choice that was made and whyconstraint— an invariant that must always hold ("never do X")directive— a soft rule or preference ("prefer Y over Z")question— an open question to revisit laterskill— a capability or competency
- Call the
addMCP tool with the text and appropriate type - If the knowledge relates to existing nodes, call
searchfirst and thenlinkto connect them - Confirm to the user what was captured and any connections made
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.
- 10d ago First seen · 23 lines · 45 tokens per session scan A 1216f6a4fdd6
kindex-capture is a skill published in the GitHub repository jmcentire/kindex (26 stars, last pushed 7d ago), licensed MIT. It adds 45 tokens to every session and 228 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.