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 agentmods add commands/johnnywuj81/tokenknows/incidentgit clone --depth 1 https://github.com/johnnywuj81/tokenknowsWrote 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/commands/johnnywuj81/tokenknows/incident)<a href="https://agentmods.dev/commands/johnnywuj81/tokenknows/incident"><img src="https://agentmods.dev/badge/commands/johnnywuj81/tokenknows/incident.svg" alt="Measured on agentmods" 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 | $0.00047 | $0.00204 |
| Opus 5 | $0.00023 | $0.00102 |
| Sonnet 5 | $0.00009 | $0.00041 |
| Haiku 4.5 | $0.00005 | $0.00020 |
Grade A, and why
incident 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 4d 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
按 tokenknows:distill skill 的标准流程,把当前 session 蒸馏成 incident:
incident 关键特征:
- session 应包含 报警 / 报错 → 排查 → 修复 的完整链
- 时间线信息很重要 (报警到恢复多久 / MTTR)
- 拆 event 时强调时间戳 (occurred_at), 让后端能重建时间线
- tag 用
incident/bug_fix/ 严重度 submit_session_eventsdistill_document(document_type="incident", time_window=$ARGUMENTS 默认 last_7_days)- 展示 6 段
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.
- 4d ago First seen · 16 lines · 47 tokens per session scan A bddfc6f5caed
incident is a command published in the GitHub repository johnnywuj81/tokenknows (4 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 204 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-31.
Other commands, from other repositories
upgrade
Upgrade the skillshare CLI binary and/or the built-in skillshare skill.
release
Walk the llmwiki release process step by step.
add-agent
引导新增一个 Agent 适配器。用法 /add-agent.
migrate
Command "migrate" from chohra-med/expo_boilerplate, covering invocation, steps and rule.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.
t800-onboard
Для чата с новичками. Показывает, что настроено в Cursor (global + local), и что умеет отдел T-800.