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 bartolli/kmd --skill triagegit clone --depth 1 https://github.com/bartolli/kmdWrote 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/bartolli/kmd/triage)<a href="https://agentmods.dev/skills/bartolli/kmd/triage"><img src="https://agentmods.dev/badge/skills/bartolli/kmd/triage/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/bartolli/kmd/triage"><img src="https://agentmods.dev/badge/skills/bartolli/kmd/triage.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.00212 | $0.03917 |
| Opus 5.5 | $0.00085 | $0.01567 |
| Sonnet 5.5 | $0.00042 | $0.00783 |
| Haiku 4.5 | $0.00021 | $0.00392 |
Grade A, and why
triage 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 — 359 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage — Move Stories Through the State Machine
A small state machine over wiki story files. Lifts Matt Pocock's triage pedagogy onto the wiki's kind: story artifact.
Prerequisites
WIKI_SCOPE: <scope>declared in the project instructions. If missing, suggest/wiki.- At least one intent under
projects/<scope>/intent/or one story file underprojects/<scope>/plan/<plan-name>/. With neither, suggest/to-stories.
Roles
Intents carry no triage labels; their state is status plus one outcome field ([[adr-intent-kind]]):
draft— filed, unread by triageactive— scheduled: accepted, story not yet writtenarchivedwith exactly one ofpromoted_to(story slug),dismissed(reason),fixed_by(regression test path)supersededwithsuperseded_by— merged into another intent, whosesightingsabsorbed the count
Stories carry two label roles.
Two category roles (story has exactly one):
bug— something is brokenenhancement— new feature or improvement
Five state roles (story has exactly one, lives in triage_state frontmatter):
needs-triage— story needs evaluationneeds-info— agent waits on user clarification (in a solo-operator context: the agent is blocked on a user decision)ready-for-agent— fully specified, AFK-ready (an agent can pick it up with no human context)ready-for-human— needs human implementation (judgment, external access, hardware, design review)wontfix— will not be actioned
State transitions: an unlabeled or needs-triage story moves to needs-info, ready-for-agent, ready-for-human, or wontfix. needs-info returns to needs-triage once the user provides the missing input. The user can override at any time — flag transitions that look unusual and confirm before proceeding.
AI disclaimer (GH/GitLab mode only)
When WIKI_ISSUE_TRACKER is github or gitlab, every comment posted to the remote tracker during triage must start with:
> *This was generated by AI during triage.*
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 ba066b0ea18f
- 1mo ago Changed 130cf9b22604
- 1mo ago Changed · +69 lines · +46 tokens per session 15c0d5db9362
- 2mo ago First seen · 290 lines · 166 tokens per session scan A 4528a18a7cf9
triage is a skill published in the GitHub repository bartolli/kmd (7 stars, last pushed 1mo ago), licensed MIT. It adds 212 tokens to every session and 3,917 once invoked, about $0.0008 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.