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 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/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/ericrisco/rsc-harness/knowledge-ops"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/knowledge-ops.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.00082 | $0.02716 |
| Opus 5.5 | $0.00033 | $0.01086 |
| Sonnet 5.5 | $0.00016 | $0.00543 |
| Haiku 4.5 | $0.00008 | $0.00272 |
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 25d 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 — 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.mdfortechnical_level, which sets your register (technical terms, or plain words with analogies). Why: a non-technical owner needs each decision explained with an analogy; a technical one reads the term directly. Either way, speak in theorientvoice: short, and every answer understandable on its own. - 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.
- 25d ago Changed a600e1461f37
- 1mo ago First seen · 123 lines · 82 tokens per session scan A 2e421a1b9a5e
knowledge-ops is a skill published in the GitHub repository ericrisco/rsc-harness (374 stars, last pushed today), licensed MIT. It adds 82 tokens to every session and 2,716 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
managing-mcp-servers
Use when the user asks to add, change, remove, enable or disable an MCP server, or when an MCP tool is missing, needs sign-in, fails, or was blocked. ThinkRail runs pi in-process, so there is no pi command to call.
wiki-lint
Audit wiki health: broken links, orphans, contradictions, stale content, lifecycle and tag issues. Use for maintenance or health checks. Default is report-only; use wiki-dedup for page-identity merges.
wiki-status
Report wiki ingestion/completeness state, pending source delta, structural insights, or maintenance equilibrium. Use for remaining-work/status questions, hubs and bridges, or whether maintenance skills still have pending changes. wiki-digest summarizes learned knowledge instead.
wiki-dashboard
Create dynamic, queryable Obsidian dashboard views using Bases or Dataview. Use for auto-updating tables, indexes, or structured views of vault content; not for ordinary question answering.
hermes-history-ingest
Ingest Hermes agent history into Obsidian as distilled knowledge. Use for importing or mining /.hermes sessions, memories, or logs; use wiki-agent for targeted topic-only cross-agent recall.
wiki-narrate
Turn a wiki topic into a cited Markdown briefing, plain-language explanation, or progressive lecture. Use this skill for topic-based briefing, explanation, and lecture requests that must stay within the evidence compiled in an Obsidian vault.