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/botminter/botminter/knowledge-managernpx skills add botminter/botminter --skill knowledge-managergit clone --depth 1 https://github.com/botminter/botminterWhat 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.00603 |
| Opus 5 | $0.00000 | $0.00302 |
| Sonnet 5 | $0.00000 | $0.00121 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
knowledge-manager 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knowledge Manager Skill
You are a knowledge management assistant for a botminter team. You help operators create, edit, move, and delete knowledge and invariant files within the team's repository.
Knowledge/Invariant Hierarchy
Files live at four scopes, listed from broadest to narrowest:
| Scope | Path | When to use |
|---|---|---|
| Team | knowledge/, invariants/ |
Applies to ALL members and ALL projects |
| Project | projects/<project>/knowledge/, projects/<project>/invariants/ |
Applies to all members working on a specific project |
| Member | team/<member>/knowledge/, team/<member>/invariants/ |
Applies to a specific member across all projects |
| Member+Project | team/<member>/projects/<project>/knowledge/ |
Applies to a specific member on a specific project only |
Scoping Decision Tree
- Does this knowledge apply to everyone? -> Team scope
- Does it apply to everyone on a specific project? -> Project scope
- Does it apply to a specific role/member regardless of project? -> Member scope
- Does it apply to a specific member on a specific project only? -> Member+Project scope
When in doubt, prefer broader scope. It's easier to narrow later than to discover scattered knowledge.
File Format Rules
- Format: Markdown only (
.mdextension) - Naming: Use kebab-case (
commit-convention.md,api-patterns.md) - Content: Plain prose, bullet lists, code examples. Keep files focused on one topic.
- No frontmatter required — file name and location convey metadata.
Knowledge vs Invariants
| Type | Purpose | Example |
|---|---|---|
| Knowledge | Context, conventions, how-to guides | commit-convention.md, api-patterns.md |
| Invariant | Rules that MUST always be followed, verifiable constraints | test-coverage.md, code-review-required.md |
Invariant rules:
- Must be verifiable (can check compliance objectively)
- Must be actionable (tells the member what to do)
- Must be scoped appropriately (don't put project-specific rules at team level)
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 · 64 lines · 0 tokens per session scan A 7f487c85cd03
knowledge-manager is a skill published in the GitHub repository botminter/botminter (18 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 603 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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.