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 skills add drn/dots --skill knowledgegit clone --depth 1 https://github.com/drn/dotsWrote 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/drn/dots/knowledge)<a href="https://agentmods.dev/skills/drn/dots/knowledge"><img src="https://agentmods.dev/badge/skills/drn/dots/knowledge/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/drn/dots/knowledge"><img src="https://agentmods.dev/badge/skills/drn/dots/knowledge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00026 | $0.00861 |
| Opus 5.5 | $0.00010 | $0.00344 |
| Sonnet 5.5 | $0.00005 | $0.00172 |
| Haiku 4.5 | $0.00003 | $0.00086 |
Grade A, and why
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 1mo 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knowledge Base
Manage a structured knowledge base at context/knowledge/ for capturing durable facts, entities, and patterns across sessions.
Arguments
$ARGUMENTS- Subcommand:init,add <topic>,update <topic>, or omit for status
Context
- Knowledge index: !
cat context/knowledge/index.md 2>/dev/null | head -50 - Knowledge files: !
find context/knowledge -maxdepth 1 -name "*.md" 2>/dev/null | head -20 - Project root: !
git rev-parse --show-toplevel 2>/dev/null | head -1 - CLAUDE.md exists: !
find . -maxdepth 1 \( -name CLAUDE.md -o -name AGENTS.md \) 2>/dev/null | head -2
Instructions
Subcommand: init
Create the knowledge base directory and seed it with an index file.
- Create
context/knowledge/directory - Write
context/knowledge/index.mdwith this template:
# Knowledge Index
Structured knowledge for future knowledge graph ingestion. Each file covers a topic/domain.
| File | Topic | Key Entities | Last Updated |
|------|-------|-------------|-------------|
## Coverage Map
Which context files are captured in knowledge:
| Context File | Knowledge File(s) | Coverage |
|-------------|-------------------|----------|
- If the project has a
.gitignore, verifycontext/knowledge/is not ignored - Report the path created and suggest initial topics based on what is visible in the repo (CLAUDE.md, AGENTS.md, README, directory structure)
Subcommand: add
Create a new topic file and register it in the index.
- Read the existing index to avoid duplicates
- Ask what entities and facts to capture if not obvious from conversation context
- Create
context/knowledge/<topic>.mdwith a heading and structured content - Update
context/knowledge/index.md— add a row to the index table with the file name, topic description, key entities, and today's date - Report what was added
Subcommand: update
Update an existing topic file with new knowledge.
- Read
context/knowledge/index.mdto find the topic file - Read the topic file
- Propose additions or corrections as diffs
- Apply after user approval
- Update the Last Updated date in
context/knowledge/index.md
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.
- 1mo ago First seen · 117 lines · 26 tokens per session scan A e8e66b762122
knowledge is a skill published in the GitHub repository drn/dots (23 stars, last pushed 11d ago), licensed MIT. It adds 26 tokens to every session and 861 once invoked, about $0.0001 per session on Opus 5.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
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
shellm
Reference for the shellm system — recursive LLM shell, identity management, memory, skills, trajectory, and all CLI tools. Use when working on shellm itself, debugging agent behavior, or understanding how the pieces fit together.