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/r5rana/agentware/knowledge-basenpx skills add r5rana/agentware --skill knowledge-basegit clone --depth 1 https://github.com/r5rana/agentwareWhat 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.00000 | $0.03153 |
| Opus 5 | $0.00000 | $0.01577 |
| Sonnet 5 | $0.00000 | $0.00631 |
| Haiku 4.5 | $0.00000 | $0.00315 |
Grade A, and why
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 3d 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 — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knowledge Base Management Skill
Overview
The knowledge base is agentware's long-term memory across sessions. It does NOT live in this repo — it lives in an EXTERNAL directory the operator chose at onboarding. Resolve that directory at runtime:
KDIR="$(scripts/agentware config --knowledge-dir-only)"
It holds context about the user, their projects, technical learnings, and
configurations. AI agents consult it before starting work and update it after
completing work so future agents inherit the context. NEVER commit knowledge
into this repo; it stays in $KDIR.
Directory layout (inside $KDIR)
$KDIR/
├── MAIN.md # Active work entry point — read first; injected on every session
├── index.json # Searchable metadata index (entries, tags)
├── FEATURES.md # Generated table of contents (scripts/agentware features)
├── .initialized # Sentinel written at the end of onboarding
├── learnings/ # Technical knowledge (one .md per topic)
├── projects/ # Active project context (one folder per project)
├── configurations/ # Service / environment configs
├── prompts/ # Reusable prompts
├── references/ # External references / pointers
├── skills/ # User/agent-created reusable procedures (category: skills)
├── templates/ # Entry templates installed at init (self-contained)
├── work/ # Per-feature plans/worklogs/state (<feature>/plan.md, .loop/)
└── logs/ # prompts.log + sessions/<id>/{main,full}.md + per-subagent transcripts
Everything mutable lives here. The orchestrator package stays read-only during normal use; only an explicit, !! WARNING !!-gated self-extension changes it.
scripts/agentware init scaffolds this. Onboarding seeds the first entries based
on the interview; the loop adds to it over time.
index.json schema
Every entry is registered in $KDIR/index.json. Paths are stored RELATIVE to
$KDIR so the index stays portable:
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.
- 3d ago First seen · 288 lines · 0 tokens per session scan A 3e150ffcba60
knowledge-base is a skill published in the GitHub repository r5rana/agentware (24 stars, last pushed 16d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,153 tokens. 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
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…