open

A command for opening one distilled project document and showing all of its chapter content. It also provides extra information for knowledge graphs, which map entities and their relationships across documents.

In plain words
What is it for?
Opening an asset by ID, viewing its Markdown chapters, and checking node and relationship counts for knowledge graphs.
Why use it?
It lets you inspect the complete details behind an item found in the document list.

Command

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.

agentmods
npx agentmods add commands/johnnywuj81/tokenknows/open
Clone the repo
git clone --depth 1 https://github.com/johnnywuj81/tokenknows
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 230 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00025 $0.00230
Opus 5 $0.00013 $0.00115
Sonnet 5 $0.00005 $0.00046
Haiku 4.5 $0.00003 $0.00023

Measured 2d ago against content hash ba5a23681267, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

open 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 2d 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.

tokenknows-plugin/commands/open.md · 15 lines

What it actually says

先校验 $ARGUMENTS:

  • 期望格式: asset-<12-16 hex chars>demo-{kg,wr}-NNN (e.g. asset-3d6cf67d96, demo-kg-001)
  • 若含 ;, |, &, $, ```, 引号, 空格 或换行 等可疑字符, 拒绝 并提示 "asset_id 格式异常, 用 /tokenknows:list 查可用 id"
  • 若为空, 提示 "请传 asset_id, 用 /tokenknows:list 看可用 id"

校验通过后调 MCP tool get_asset_chapters("$ARGUMENTS"),展示所有章节 markdown.

如果是 knowledge_graph 类型, 额外:

  • 简述节点/边统计
  • 询问用户是否要 search_entity 查特定实体跨文档出现
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. 2d ago First seen · 15 lines · 25 tokens per session scan A ba5a23681267

Subscribe to this mod's changes

open is a command published in the GitHub repository johnnywuj81/tokenknows (4 stars, last pushed 13d ago), licensed MIT. It adds 25 tokens to every session and 230 once invoked, about $0.0001 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.