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/ericrisco/rsc-harness/knowledge-opsnpx skills add ericrisco/rsc-harness --skill knowledge-opsgit clone --depth 1 https://github.com/ericrisco/rsc-harnessWrote 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/ericrisco/rsc-harness/knowledge-ops)<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/knowledge-ops"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/knowledge-ops.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.00082 | $0.02686 |
| Opus 5 | $0.00041 | $0.01343 |
| Sonnet 5 | $0.00016 | $0.00537 |
| Haiku 4.5 | $0.00008 | $0.00269 |
Grade A, and why
knowledge-ops 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 today.
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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knowledge Ops — Garden the 02-DOCS Wiki
The engine is already running. harness built the 02-DOCS/ wiki and owns its automation — the inbox sweep, deterministic lint, scoring, gap detection, the self-improve loop — and changing that machinery or filling the wiki in bulk stays with it. Yours are the four judgments automation deliberately leaves to a human: what is worth capturing, how it should be shaped, how it connects, and what should retire. You are the gardener, not the machinery.
Before you touch anything
- Confirm
02-DOCS/wiki/exists. If there is no wiki, stop and say: "Runharnessto build the02-DOCS/wiki first, then come back to garden it." Why: this skill operates an existing engine; it never creates one. See../harness/SKILL.md. - Read
wiki/harness/user-profile.mdto set your verbosity (the harness accompaniment dial, L0–L3). Why: a non-technical owner wants decisions narrated; an expert wants terse diffs. - Read
wiki/index.mdandwiki/scores.jsonbefore any edit. Why: you garden from the map and the score signal, never blind.scores.jsontells you what is bloated, orphaned, or stale.
If wiki/log.md shows a Maintenance Pass ran in the last few minutes, let it finish — do not race the automation.
The four operations
Every gardening request is one of four operations. Identify which before you act.
| Operation | You are doing this when… | Primary signal | Writes to |
|---|---|---|---|
| Capture | A note/source needs a decision: keep, where, at what altitude | new content in inbox//raw/ or a loose user note |
raw/ and/or wiki/<topic>/<article>.md |
| Structure | An article is bloated, mistitled, or duplicated | length, a non-singular Overview, near-duplicate titles | wiki/<topic>/, _archive/ |
| Link | Pages are unreachable or under-connected | scores.json orphan_penalty (=5), low inbound count |
## See Also in articles, index.md |
| Prune | Answers are stale, articles superseded, conflicts unresolved, gaps bloated | freshness, conflict annotations, old [FILLED] gaps |
_archive/, log.md, gaps.md |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 123 lines · 82 tokens per session scan A 2e421a1b9a5e
knowledge-ops is a skill published in the GitHub repository ericrisco/rsc-harness (60 stars, last pushed yesterday), licensed MIT. It adds 82 tokens to every session and 2,686 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
llm-wiki
The foundational knowledge distillation pattern for building and maintaining an AI-powered Obsidian wiki. Based on Andrej Karpathy's LLM Wiki architecture. Use this skill whenever the user wants to understand the wiki pattern, set up a new knowledge base, or needs guidance on the three-layer architecture (raw sources…
wiki-lint
Audit and maintain the health of the Obsidian wiki. Use this skill when the user wants to check their wiki for issues, find orphaned pages, detect contradictions, identify stale content, fix broken wikilinks, or perform general maintenance on their knowledge base. Also triggers on "clean up the wiki", "what needs…
wiki-status
Show the current state of the wiki — what's been ingested, what's pending, and the delta between sources and wiki content. Use this skill when the user asks "what's the status", "how much is ingested", "what's left to process", "show me the delta", "what changed since last ingest", "wiki dashboard", or wants an…
wiki-export
Export the Obsidian wiki's knowledge graph to structured formats for use in external tools. Use this skill when the user says "export wiki", "export graph", "export to JSON", "export to Gephi", "export to Neo4j", "export to Postgres", "export to SQL", "graphml", "visualize wiki", "knowledge graph export", "export to…
wiki-query
Answer questions by searching the compiled Obsidian wiki. Use this skill when the user asks a question about their knowledge base, wants to find information across their wiki, asks "what do I know about X", "find everything related to Y", or wants synthesized answers with citations from their wiki pages. Also use when…
copilot-history-ingest
Ingest GitHub Copilot CLI session history into an Obsidian wiki as distilled knowledge pages. Use this skill when the user wants to capture their Copilot CLI sessions into a personal wiki — extracting architecture decisions, debug notes, and patterns into searchable Obsidian pages. Triggers on phrases like "ingest my…