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/usefulmove/enso/document-knowledge-basenpx skills add usefulmove/enso --skill document-knowledge-basegit clone --depth 1 https://github.com/usefulmove/ensoWhat 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.00054 | $0.02529 |
| Opus 5 | $0.00027 | $0.01264 |
| Sonnet 5 | $0.00011 | $0.00506 |
| Haiku 4.5 | $0.00005 | $0.00253 |
Grade A, and why
document-knowledge-base 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.
How it starts
The opening of the file, as written. The whole thing — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
Load this skill when:
- Asked to create or update a knowledge base
- Documenting a codebase, system, API, domain, or process for the first time
- Refreshing a KB entry that may be stale
- Bootstrapping a
docs/core/architecture/structure in a new project
The Core Idea
A knowledge base is not a library. It's a web.
Coverage is not the goal. The value is in the connections between entries — the relationships that let an agent (or a human) navigate from what they know to what they need. An entry with five accurate cross-references is worth more than a comprehensive entry with none.
Core Concepts
Entry Lifecycle
Every KB entry has a status:
| Status | Meaning |
|---|---|
stub |
Node is known to exist; not yet documented |
draft |
Documented from discovery; not yet verified against source |
verified |
Confirmed accurate against source |
stale |
Previously accurate; source has changed |
Recommended Frontmatter
Keep frontmatter minimal. These fields matter for KB health:
---
title: <human-readable name>
source: <path, URL, or concept identifier — whatever was probed>
status: stub | draft | verified | stale
related: [<other entry paths or titles>]
last_updated: <YYYY-MM-DD>
---
Add domain-specific fields as needed (e.g., tags, owner, version). Don't over-engineer frontmatter for a first pass — status and last_updated are the minimum viable fields.
Naming for Navigability
KB entries and files are discovered by name before their content is read. Names should be self-describing.
Entry names (titles and filenames):
- Use the subject's actual name, not a generic label:
websocket-communicationnotlayer-3 - Prefer noun phrases that match how the subject is referred to in the codebase or domain
- Avoid abbreviations unless they're universally understood in context
- Directory names should match the entry title in kebab-case:
websocket-communication/README.md
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.
- yesterday First seen · 327 lines · 54 tokens per session scan A b0e03fe2b75b
document-knowledge-base is a skill published in the GitHub repository usefulmove/enso (2 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 2,529 once invoked, about $0.0003 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
harness-creator
Build, audit, and improve harnesses that make AI coding agents reliable: AGENTS.md/CLAUDE.md instruction files, feature/state tracking, verification gates, scope boundaries, session handoff, memory persistence, context budgets, tool-permission safety, and multi-agent coordination. Use this whenever a coding agent is…
harness
하네스를 구성합니다. 전문 에이전트를 정의하며, 해당 에이전트가 사용할 스킬을 생성하는 메타 스킬. (1) '하네스 구성해줘', '하네스 구축해줘' 요청 시, (2) '하네스 설계', '하네스 엔지니어링' 요청 시, (3) 새로운 도메인/프로젝트에 대한 하네스 기반 자동화 체계를 구축할 때, (4) 하네스 구성을 재구성하거나 확장할 때, (5) '하네스 점검', '하네스 감사', '하네스 현황', '에이전트/스킬 동기화' 등 기존 하네스 운영/유지보수 요청 시 사용.
pr-review
Review a GitHub pull request and post a verdict comment. Stateful — if a previous review comment exists, review only the new commits since the last review and track whether prior findings were addressed. Focus on code cleanliness, duplication, and docs sync. Use when user says "review this PR", "check the PR", "leave…
cc10x-router
THE ONLY ENTRY POINT FOR CC10X. Activate this skill for build, debug, review, and plan requests. Use when the user asks to implement, fix, review, plan, test, refactor, or continue code work. Trigger keywords: build, implement, create, write, add, review, audit, debug, fix, error, bug, broken, plan, design, architect…
new-plugin
Factory line for adding a new HAR verification plugin (like playwright or rocketsim) for any framework — research the framework docs, build the template under src/templates/plugins/, register it everywhere, validate on a real repository, and open a PR. Use when asked to add/create a plugin, plugin template, or…
building
Implementation skill for writing production code with TDD. Covers the RED-GREEN-REFACTOR cycle, false-RED detection, vertical slicing, scope escalation, test process discipline, and code generation patterns. Loaded by component-builder and bug-investigator.