tokenknows

A Claude plug-in that turns a coding session into structured documents through a self-hosted service. It can produce weekly reports, technical plans, architecture decision records, retrospectives, books, skills, and knowledge graphs.

In plain words
What is it for?
Use it to distill a session into project documentation or a knowledge graph. It requires the TokenKnows backend, web workspace, and uv setup.
Why use it?
It organizes scattered session details into reusable written knowledge instead of leaving decisions and lessons buried in chat.

Plugin for Claude Code

Install

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.

Claude Code
/plugin marketplace add johnnywuj81/tokenknows
agentmods
npx agentmods add plugins/johnnywuj81/tokenknows/tokenknows-plugin
Clone the repo
git clone --depth 1 https://github.com/johnnywuj81/tokenknows

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

tokenknows 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 yesterday.

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.

tokenknows-plugin/.claude-plugin/plugin.json · 20 lines

What it actually says

{
  "name": "tokenknows",
  "version": "2.2.0",
  "description": "把当前 Claude session 蒸馏成结构化文档 (周报 / 技术方案 / ADR / 复盘 / 书籍 / Skill / 知识图谱), 通过 MCP 接 tokenknows-api 后端 5-stage pipeline. 前置: 自托管后端 + Web 工作台 + uv, 详见 README.",
  "author": {
    "name": "TokenKnows",
    "url": "https://github.com/johnnywuj81/tokenknows"
  },
  "homepage": "https://github.com/johnnywuj81/tokenknows/tree/main/tokenknows-plugin",
  "repository": "https://github.com/johnnywuj81/tokenknows",
  "license": "MIT",
  "keywords": [
    "knowledge-distill",
    "weekly-report",
    "adr",
    "knowledge-graph",
    "mcp"
  ]
}
Changes

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.

  1. yesterday First seen · 20 lines scan A cc6e443cbd49

Subscribe to this mod's changes

tokenknows is a plugin published in the GitHub repository johnnywuj81/tokenknows (4 stars, last pushed 13d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.