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 skills/kreek/consult/documentationnpx skills add kreek/consult --skill documentationgit clone --depth 1 https://github.com/kreek/consultWhat 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.00024 | $0.01330 |
| Opus 5 | $0.00012 | $0.00665 |
| Sonnet 5 | $0.00005 | $0.00266 |
| Haiku 4.5 | $0.00002 | $0.00133 |
Grade A, and why
documentation 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.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation
Iron Law
DOCUMENT ONLY WHAT NEEDS PROSE. KEEP DOCS NEAR THE CODE, CONTRACT, OR TEAM THAT MAINTAINS THEM.
When to Use
- The user asks for or approves writing/reviewing READMEs, runbooks, tutorials, how-to guides, reference docs, module docs, or code comments: documentation that describes code and systems as they exist.
- Authoring or revising Consult SKILL.md files; skills are documentation for agents and follow the same clarity rules.
- Deciding whether prose is needed or whether a type, schema, generated reference, test, or command output should be the source of truth.
When NOT to Use
- Forward-looking documents that record decisions or propose futures: design docs, ADRs, RFCs, tech specs, PRDs, requirements, acceptance criteria, system analyses, strategy. Consult does not cover these; use a dedicated writing skill if one is installed, such as Terse.
- Ordinary implementation where docs might later be useful but were not requested, approved, or required by a validator. Name the possible docs gap in the final response instead of editing docs.
- API contract design; use
api. - Release coordination, changelog process, release notes, version manifests,
or migration notes; use
release. Those artifacts land only during release prep. - Alert mechanics and dashboards; use
observability.
Core Ideas
- Documentation is a separate work product, not an implementation reflex. Before editing docs outside the user's request, ask whether docs are in scope unless a repo validator requires the update.
- Living documentation has an owner, a nearby source of truth, and a change path; orphaned prose becomes misinformation.
- One doc has one reader situation: tutorial, how-to, reference, explanation, or runbook.
- Build the reader's knowledge in layers. Name the starting point, introduce terms before relying on them, and move from prerequisite concepts to working steps to deeper reference. Do not make readers infer the path.
- Link to source-of-truth artifacts instead of restating generated facts. Put docs next to the code or service whose reviewers can catch drift.
- Write the why, context, and tradeoffs; let code/tests/schemas prove mechanics.
- Voice and prose structure: plain, direct, concrete sentences, no em dashes, only words that earn their place.
- Delete stale docs when you cannot fix them now.
- Comments explain why and how when names, types, schemas, tests, or local structure cannot. Encode the rule in code or tests first; add a comment only when the reason remains non-obvious.
- Runbooks are operational artifacts: symptom, diagnosis, remediation, verification, escalation.
- Large project docs use the repo's existing docs system. If none exists, choose one during scaffolding or with user approval.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 120 lines · 24 tokens per session scan A fe2bb970a3d9
documentation is a skill published in the GitHub repository kreek/consult (1 stars, last pushed 7d ago), licensed MIT. It adds 24 tokens to every session and 1,330 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.
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.
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.
review
5-pass structured code review — correctness, security, performance, readability, consistency.
scaffold
Project-aware file generation. Reads existing codebase conventions (naming, structure, imports, exports, test patterns) then generates new files that match exactly. Wires generated files into the project's registration points.
marshal
Meta-orchestrator that takes any direction — broad, specific, or vague — and autonomously chains skills and context into actionable work. Gathers context from codebase, docs, and memory. Only asks the user when it genuinely cannot proceed. Single-session orchestrator.
organize
Repository structure only: directory layout, file placement, naming conventions, and where-does-this-belong decisions. Detects the project's convention, audits files against it, and executes move plans with import-path updates. Never changes code inside files beyond the import updates a move forces; in-file…