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/runwhen-contrib/runwhen-platform-mcp/manage-knowledgenpx skills add runwhen-contrib/runwhen-platform-mcp --skill manage-knowledgegit clone --depth 1 https://github.com/runwhen-contrib/runwhen-platform-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/runwhen-contrib/runwhen-platform-mcp/manage-knowledge)<a href="https://agentmods.dev/skills/runwhen-contrib/runwhen-platform-mcp/manage-knowledge"><img src="https://agentmods.dev/badge/skills/runwhen-contrib/runwhen-platform-mcp/manage-knowledge.svg" alt="Measured on agentmods" height="20"></a>What 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.00094 | $0.01639 |
| Opus 5 | $0.00047 | $0.00820 |
| Sonnet 5 | $0.00019 | $0.00328 |
| Haiku 4.5 | $0.00009 | $0.00164 |
Grade A, and why
manage-knowledge 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 4d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage Knowledge
Knowledge Base (KB) articles are durable operational facts indexed into the workspace's Knowledge Overlay Graph. They improve investigation quality by providing context that can't be inferred from diagnostic output alone — the kind of information that lives in your team's heads rather than in task results.
When to use
- User says "remember this", "note that", "add context about..."
- Investigation quality suffers because the assistant lacks institutional context
- Architecture, ownership, or process knowledge needs documenting
- Temporary operational notes for releases, incidents, or maintenance windows
- Replacing the
/remembercommand from workspace chat UI with API-driven KB management
Key concepts
Knowledge vs Rules vs Commands
| Type | Purpose | Loaded when |
|---|---|---|
| Rules | Short behavior directives (1-3 sentences) — noise suppression, priority framing | Every response, always |
| Commands | Multi-step investigation procedures | When user invokes /command |
| Knowledge | Durable facts — architecture, ownership, processes, dependencies | When relevant resource is identified (resource-scoped) or always (global) |
If it's a behavior instruction ("prioritize X over Y"), use a Rule. If it's a procedure ("do steps 1-2-3"), use a Command. If it's a fact ("service X depends on Y, owned by team Z"), use Knowledge.
Resource scoping via resource_paths
KB articles can be scoped to specific infrastructure resources. The resource_paths
field links an article to canonical resource paths (same format as SLX resourcePath).
| Scope | resource_paths |
When loaded |
|---|---|---|
| Global | [] (empty) |
Every investigation |
| Resource-scoped | ["kubernetes/cluster-01/payments"] |
Only when the assistant investigates that resource |
Resource scoping keeps context lean — global knowledge provides the baseline, resource-specific knowledge is loaded dynamically as the investigation narrows.
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.
- 4d ago First seen · 159 lines · 94 tokens per session scan A 78bb72dd490c
manage-knowledge is a skill published in the GitHub repository runwhen-contrib/runwhen-platform-mcp (1 stars, last pushed 21d ago), licensed Apache-2.0. It adds 94 tokens to every session and 1,639 once invoked, about $0.0005 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
memory-audit-pattern-extraction
模式提取与失效解药分析。当发现多条记忆在讲同一个教训，或发现自己在一而再再而三地犯同样的错误时使用。.
init-workspace-documentation
Skill "init-workspace-documentation" from griddynamics/rosetta, covering agent memory.md, agent memory, preventive rules, what worked and what failed.
memorix-mini-skills
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.
frontmcp-extensibility
Use when extending FrontMCP beyond the core SDK by integrating external npm packages, libraries, or third-party services into providers and tools. Covers VectoriaDB for in-memory semantic and vector search (ML-based embeddings or TF-IDF keyword engines, with persistence) and the tamper-evident, hash-chained skill…
frontmcp-testing
Use for anything about testing FrontMCP servers: writing or running unit, integration, and E2E tests and reaching the 95%+ coverage bar. Covers Jest setup and coverage gating; unit-testing a ToolContext execute() with mock context, inputs, and Zod schema validation; testing resources and prompts; in-memory testing via…