extract

A command that extracts reusable ideas from personal or work documents and saves them as general knowledge in a wiki. It removes company names, specific data, and internal terms before recording the result.

In plain words
What is it for?
Use it to turn project notes, business documents, or personal materials into reusable architecture principles, design decisions, and business insights.
Why use it?
It helps preserve useful patterns without copying private or project-specific details into the knowledge base. It also records where the extracted knowledge came from.

Command

Part of the flolib-skills plugin — 6 skills, 4 commands shipped together

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/wunamesst/skills/extract
Clone the repo
git clone --depth 1 https://github.com/wunamesst/skills

Or install flolib-skills, the plugin that ships this one along with the rest of its 6 skills, 4 commands.

Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 217 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.00023 $0.00217
Opus 5 $0.00012 $0.00109
Sonnet 5 $0.00005 $0.00043
Haiku 4.5 $0.00002 $0.00022

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

Security

Grade A, and why

extract 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 3d 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.

plugins/poly-wiki/skills/poly-wiki/commands/extract.md · 19 lines

What it actually says

从个人项目或工作文档中萃取可复用的知识模式:

  1. 确认用户授权(本命令即视为授权)
  2. 读取来源路径下的文件
  3. 剥离业务属性(公司名、具体数据、内部术语)
  4. 提炼通用模式、架构原则、设计决策
  5. 写入 02_Wiki/项目知识/02_Wiki/业务洞察/
  6. Frontmatter 标注 [业务萃取][个人萃取]
  7. 追加 00_SYSTEM/INGEST_LOG.md

示例: /wiki:extract 04_Work/51Talk/CRM/capacity 业务洞察

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. 3d ago First seen · 19 lines · 23 tokens per session scan A 7b4d46803169

Subscribe to this mod's changes

extract is a command published in the GitHub repository wunamesst/skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 217 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.