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/chenchihcu/devspace-mcp/knowledge-base-managementnpx skills add chenchihcu/DevSpace-MCP --skill knowledge-base-managementgit clone --depth 1 https://github.com/chenchihcu/DevSpace-MCPWhat 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.00027 | $0.00317 |
| Opus 5 | $0.00014 | $0.00159 |
| Sonnet 5 | $0.00005 | $0.00063 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
knowledge-base-management 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.
What it actually says
knowledge-base-management
Purpose
Organize reusable knowledge while keeping sources, naming, and archive decisions traceable.
When to Use
- Updating inbox, source register, index, or topic map documents.
- Planning naming conventions, folder organization, and archive recommendations.
- Connecting new case material to reusable knowledge.
Inputs
- Workspace structure and project instructions.
- Source files or incoming notes.
- Naming, indexing, or archive objective.
Outputs
- Index update plan.
- Source register entries.
- Topic map changes.
- Archive or naming recommendations with rationale.
Workflow
- Inspect project rules before changing structure.
- Register sources before turning them into reusable knowledge.
- Keep archive/delete recommendations separate from execution.
- Use guarded file operations for any write, move, rename, mkdir, or delete.
Verification
- Confirm every index entry points to an existing source.
- Confirm naming follows workspace rules.
- Confirm archive/delete actions have dry-run or approval evidence.
Risks / Limits
- Poor source registration reduces traceability.
- File moves and deletes are high risk and require guarded action.
- Do not collapse distinct source meanings during summarization.
Forbidden Actions
- Do not delete, move, or rename without guarded tools.
- Do not touch protected paths.
- Do not invent source metadata.
Example Task
Add a new supplier report to the source register and propose topic map updates.
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 · 51 lines · 27 tokens per session scan A 49c3bb75a752
knowledge-base-management is a skill published in the GitHub repository chenchihcu/DevSpace-MCP (0 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 317 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
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.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…