doc

A project-document workflow for creating, editing, tracking, and querying documents under a docs/ folder.

In plain words
What is it for?
Use it for design documents, requests for comments, marketing documents, status changes, and questions about which project documents exist or are complete.
Why use it?
It keeps each document's status and metadata consistent and maintains the folder's generated index.

Skill for Claude CodeCodex

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 skills/termio-sh/termio/doc
Any agent
npx skills add termio-sh/termio --skill doc
Clone the repo
git clone --depth 1 https://github.com/termio-sh/termio

Made for: Claude Code, Codex.

Per session 190 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,271 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.00190 $0.02271
Opus 5 $0.00095 $0.01136
Sonnet 5 $0.00038 $0.00454
Haiku 4.5 $0.00019 $0.00227

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

Security

Grade A, and why

doc 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.

skills/doc/SKILL.md · 167 lines

How it starts

The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Project docs — create & query

Every doc under docs/ carries its status in YAML front matter at the very top of the file. That front matter is the single source of truth — there is no central index/JSON to keep in sync. "What's done?" is answered by scanning the front matter live (see Query). This skill writes that front matter when creating a doc, and reads it when querying.

docs/README.md is the human-facing wiki for the folder: it explains the organization and holds a generated index table between <!-- BEGIN docs-index --> / <!-- END docs-index --> markers. That table is a derived view, not a source of truth — regenerate it from front matter (see Maintain the wiki index); never hand-edit the rows.

Front matter schema

---
title: <free text — the human title>
status: draft        # see vocabulary below
type: design         # design | rfc | marketing
created: 2026-06-28  # YYYY-MM-DD, only the day the doc was first written
updated: 2026-06-28  # YYYY-MM-DD, bump on every meaningful edit
related:             # optional — sibling filenames (YYYYMMDD- prefix under design/)
  - 20260719-vibe-island-status.md
---
  • status vocabulary (a doc moves down this list over its life):
    • draft — being written, nothing committed to.
    • in-review — content complete, awaiting sign-off.
    • approved — signed off, not yet built.
    • active — currently being executed / lived against (e.g. a strategy memo).
    • done — fully delivered; kept for reference.
    • archived — superseded or abandoned; ignore for planning.
  • type is just a label on the doc; it does not dictate a subdirectory. The set is small on purpose; add a new type only when a doc genuinely doesn't fit.
  • Keys are English (tooling/Obsidian compatibility); values may be Chinese where natural (e.g. a Chinese title). Quote any value containing : # [ ].

Create a doc

All docs live somewhere under docs/. The skill does not impose a per-type folder layout — place the file under docs/ (or whichever existing docs/ subfolder the user points at), and let type in the front matter, not the path, carry the category.

Read the full file on GitHub · 167 lines

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 · 167 lines · 190 tokens per session scan A 8a97b4c9017c

Subscribe to this mod's changes

doc is a skill published in the GitHub repository termio-sh/termio (359 stars, last pushed 3d ago), licensed MIT. It adds 190 tokens to every session and 2,271 once invoked, about $0.0010 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.

Related

Other skills, from other repositories

batch

Execute batch operations on multiple files in parallel. Automatically discovers files, splits into chunks, and processes with parallel worker agents. Use /batch followed by operation and file pattern.

QwenLM/qwen-code · 37 tokens

extension-creator

Create, scaffold, customize, validate, and locally test Qwen Code extensions. Use when the user wants a new Qwen Code extension, needs help choosing an extension template, wants to add QWEN.md context, commands, skills, agents, MCP servers, settings, hooks, channels, or LSP servers, or asks how to link and test an…

QwenLM/qwen-code · 96 tokens

notion

Notion API for creating and managing pages, databases, and blocks. Use when the user wants to create a Notion page, query a Notion database, update Notion properties, search Notion, add content to Notion, manage Notion blocks, or interact with Notion data sources and workspaces via the API.

elizaOS/eliza · 69 tokens

pr-feedback

Fetches PR review feedback and inline comments, categorizes them, and presents options to the user. Use when the user asks to get, read, address, or fix review comments on a pull request.

strands-agents/harness-sdk · 44 tokens

docs

Access and update the user's Docs vaults. Use whenever the user asks to read, find, create, update, or store a note, document, plan, or HTML artifact; when a Docs @-mention appears in context; or when an answer should link to a document the user can open in Docs.

get-bb/bb · 64 tokens

dev-pain-finder

Scrape real developer pain points for any keyword, technology, or problem space from Reddit, Hacker News, dev.to, and GitHub Discussions simultaneously — then group complaints by theme, score them by frequency and upvote weight, and return a ranked opportunity map showing where developer frustration is high and…

tinyfish-io/tinyfish-cookbook · 160 tokens