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 Curt-Park/autology --skill triage-knowledgegit clone --depth 1 https://github.com/Curt-Park/autologyWrote 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/curt-park/autology/triage-knowledge)<a href="https://agentmods.dev/skills/curt-park/autology/triage-knowledge"><img src="https://agentmods.dev/badge/skills/curt-park/autology/triage-knowledge/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/curt-park/autology/triage-knowledge"><img src="https://agentmods.dev/badge/skills/curt-park/autology/triage-knowledge.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.00043 | $0.00501 |
| Opus 5 | $0.00022 | $0.00251 |
| Sonnet 5 | $0.00009 | $0.00100 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
triage-knowledge 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
Overview
Scan docs/ against conversation context or an action summary. Classify each knowledge item as existing or new, and return topology hints (connected nodes, shared tags) so sync and capture can use them during execution.
Process
1. Extract knowledge items from context
From conversation or action summary, identify:
- Decisions made, conventions established, components changed, patterns discovered
2. Search docs/ for each item
For each item:
- Grep docs/ for keywords, titles, tags
- Read matched files to confirm relevance
3. Build topology hints
For matched nodes:
- Extract wikilink connections ([[target]] patterns)
- Identify nodes sharing tags
- Flag hub/orphan status
For unmatched new items:
- Suggest related existing nodes based on tags or content overlap
4. Return classified list
Output Format
Autology — Triage Results
Existing (→ sync)
- docs/foo.md — matches [item description] Connected: [[bar]], [[baz]] | Tags: arch, api | Hub (5 links)
- docs/qux.md — matches [item description] Connected: [[foo]] | Tags: convention | Orphan-adjacent
New (→ capture)
- [item description] — no matching node Suggested relations: [[foo]], [[bar]] (shared tags: architecture)
- [item description] — no matching node Suggested relations: none
If no existing docs match any items, use empty-state format:
Autology — Triage Results
No existing matches found. All items classified as new.
New (→ capture)
- [item description] — no matching node Suggested relations: [[foo]] (shared tags: architecture)
Common Mistakes
| Mistake | Fix |
|---|---|
| Judge relevance by keyword match alone | Read the file to confirm actual relevance |
| Omit topology hints | sync/capture rely on connected/suggested relations — always include |
| Ignore implicit relations | Check tags and content overlap even without wikilinks |
What ships with it
3 files 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.
- 9d ago First seen · 67 lines · 43 tokens per session scan A 0a7171f70bd3
triage-knowledge is a skill published in the GitHub repository Curt-Park/autology (24 stars, last pushed 6mo ago), licensed MIT. It adds 43 tokens to every session and 501 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
mama-context
Always-on background context injection from MAMA memory. Automatically surfaces relevant decisions when you work on code, without explicit invocation.
mama-install
Install MAMA OS and follow its self-teaching CLI until the first report is confirmed.
vault
Search, read, write, and manage files in the Kept conversation vault. Use when the user asks about past conversations, wants to save notes, needs to find specific content, or wants to organize their vault.
kb-session-review
Review this session's knowledge base usage. Use when the user asks whether the KB was updated, what was captured, if anything was missed, or wants a session retrospective on knowledge capture quality.
wiki-retrieve
Build and query a vault-local contextual BM25 retrieval index with optional multilingual Nomic cosine reranking; use for retrieve, hybrid retrieval, BM25, rerank, contextual retrieval, chunk search, vault search, semantic search, find relevant passages, or retrieval diagnostics. Derived caches stay under .vault-meta…
memory-audit-pattern-extraction
A method for investigating repeated mistakes by comparing related memories and checking whether an earlier reminder failed. It looks at where the reminder was stored, when it was created, and whether it was strong enough to prevent the mistake.