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/charlesjones-dev/claude-code-plugins-dev/kb-listnpx skills add charlesjones-dev/claude-code-plugins-dev --skill kb-listgit clone --depth 1 https://github.com/charlesjones-dev/claude-code-plugins-devWhat 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.00030 | $0.00816 |
| Opus 5 | $0.00015 | $0.00408 |
| Sonnet 5 | $0.00006 | $0.00163 |
| Haiku 4.5 | $0.00003 | $0.00082 |
Grade A, and why
kb-list 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knowledge Base Listing
You are a knowledge base inventory assistant. Your job is to display the current state of the project's knowledge base. This is a read-only operation - no files are modified.
Instructions
CRITICAL: This command MUST NOT accept any arguments. Ignore any text provided after the command.
Step 1: Read CLAUDE.md
- Read the project's
CLAUDE.mdfile. - If no Knowledge Base section exists, inform the user: "No Knowledge Base section found in CLAUDE.md. Run
/kb-initto set one up." and stop. - Parse the Knowledge Base reference table to extract all entries (Topic, File, When to Load).
- Read
docs/kb/_global-learnings.mdif it exists for global learnings count. Also check for a legacy### Global Learningsinline section in CLAUDE.md (older setups may still have this — if found, suggest running/kb-upgradeto migrate).
Step 2: Verify File Status and Read Frontmatter
For each entry in the table:
- Check if the referenced file actually exists using Glob or Read.
- If the file exists:
- Read its YAML frontmatter to extract:
tags,related,created,last-updated,pinned,scope. - Read the first few lines after frontmatter to get its title/description.
- Mark as OK.
- Flag if frontmatter is missing or incomplete (NEEDS FRONTMATTER).
- Read its YAML frontmatter to extract:
- If the file doesn't exist, mark as MISSING.
Step 3: Scan for Orphaned Files
- Glob for all
.mdfiles underdocs/kb/(excludingdocs/kb/README.md). - Identify files that exist in
docs/kb/but are NOT referenced in the CLAUDE.md table. - Mark these as UNREGISTERED. Read their frontmatter if present.
Step 4: Display Summary
Present the results in a clear format:
Knowledge Base Status
=====================
Registered KB Files:
| Status | Topic | File | Tags | Last Updated | Pinned | When to Load |
|--------|-------|------|------|-------------|--------|--------------|
| OK | API Conventions | docs/kb/api-conventions.md | api, rest | 2026-04-01 | No | `packages/api/**` — api, rest |
| OK | Auth Rules | docs/kb/auth.md | auth, security | 2026-03-15 | Yes | Always (pinned) |
| MISSING | Old Feature | docs/kb/old-feature.md | - | - | - | — feature-x |
| NEEDS FM | Deployment | docs/kb/deployment.md | (no frontmatter) | - | - | — deployment |
Cross-References:
- docs/kb/api-conventions.md → [[auth]]
- docs/kb/auth.md → [[api-conventions]]
Unregistered Files (in docs/kb/ but not in CLAUDE.md):
- docs/kb/new-topic.md (tags: misc, workflow)
Global Learnings: {count} entries
Summary: {ok_count} registered, {missing_count} missing, {unregistered_count} unregistered, {no_frontmatter_count} missing frontmatter
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 · 71 lines · 30 tokens per session scan A a5782d88594d
kb-list is a skill published in the GitHub repository charlesjones-dev/claude-code-plugins-dev (34 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 816 once invoked, about $0.0002 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.
Other skills, from other repositories
gwm
Manage git worktrees across any repository with the gwm Rust binary (CLI + ratatui TUI). Use when the user asks to create / list / remove / bootstrap / switch / link worktrees, run a command across worktrees (gwm exec) or reclaim build artifacts (gwm clean), materialise a PR into a worktree (gwm review), drive a…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.