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/harnessnpx skills add ericrisco/rsc-harness --skill harnessgit 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/harness)<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/harness"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/harness.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.1 | $0.00094 | $0.06005 |
| Opus 5 | $0.00047 | $0.03002 |
| Sonnet 5 | $0.00019 | $0.01201 |
| Haiku 4.5 | $0.00009 | $0.00600 |
Grade B, and why
harness scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
echo " Debian/Ubuntu: sudo apt install python3" How it starts
The opening of the file, as written. The whole thing — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harness — the workspace control plane
The harness is the control plane of a workspace. A workspace need not be code: it can be a company, an ops desk, a legal archive, a personal knowledge vault. Whatever it is, the harness is the durable apparatus that keeps it operable and legible, made of three parts:
-
01-TOOLS/<PROVIDER>/— the operational tooling layer. One folder per external provider, co-locating credentials (.env) with the scripts that consume them. Each tool ships a workingtest_connectionagainst the real API. -
02-DOCS/— the Karpathy chaos→knowledge engine: a domain-agnostic LLM wiki (inbox/,raw/,raw/worklog/,wiki/with itsindex.md/log.md/gaps.md/scores.jsonand.baseviews), embedded in this skill — no external sub-skill required.Two on-ramps feed it. Ingest: the user drops any file in any format into
inbox/, and the Auto-Ingest Sweep extracts, classifies, cross-links and compiles it — then goes for a walk, discovering un-ingested documents anywhere in the workspace, bounded by.rscignore(baseline:references/ingest-ignore-defaults.md) and de-duplicated through thewiki/.ingested.jsonledger. Worklog: every meaningful session of work is itself a raw source inraw/worklog/, captured onPreCompact/SessionEnd, at a commit milestone, or by the daily curation pass.Ingest relocates, never deletes: a loose file at the workspace root moves into
raw/; a file inside a folder the user maintains is copied, and consolidating that folder needs explicit consent.The
wiki/is simultaneously an OKF-v0.1 bundle (Open Knowledge Format) and an Obsidian-native vault: markdown links, YAML frontmatter, readable filenames,.baseviews giving a real graph and live tables. Structure, not vector DB / embeddings / RAG. The agent writes it; the human reads it in Obsidian. Topics are inferred from content (finanzas/,legal/,crm/…), never hardcoded.It compounds on its own: every Ingest, Sweep and Query triggers a Maintenance Pass (lint, score recomputation, gap detection, Related sweep), a Micro-Improve runs every N interactions, and Deep Improve runs on request or on the daily schedule (
references/daily-curation-automation.md— on Claude Code, wire it via thescheduleskill). Protocol →references/wiki-protocol.md; formats →references/ingest-formats.md; capture →references/wiki-worklog-template.md; vault →references/obsidian-scaffolding.md. -
The Knowledge map — the
## Knowledge mapsection of the rootCLAUDE.mdthat indexes the wiki (including theharness/topic) and is read by every other skill before it works in its area.
harness is the protagonist concept. init is the bootstrap front door — it gauges the user, drafts the profile, and hands off the first scaffold. THIS skill (harness) is the ongoing control: it audits, migrates, scaffolds, sweeps the inbox, and keeps the wiki, the tooling and the Knowledge map honest over the life of the workspace. It also generates root CLAUDE.md and AGENTS.md, and migrates legacy XX-* numbered folders into the canonical layout.
What ships with it
28 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.
- assets/_TEMPLATE/.env.example 194 B
- assets/_TEMPLATE/.gitignore 75 B
- assets/_TEMPLATE/CREDENTIALS.md 782 B
- assets/_TEMPLATE/README.md 766 B
- assets/_TEMPLATE/test_connection.sh 812 B runs code
- evals/cases.yaml 7.2 KB
- evals/README.md 2.6 KB
- examples/audit-example.md 4.5 KB
- references/agents-md-template.md 1.3 KB
- references/audit-report-template.html 8.0 KB
- references/audit-report-template.md 3.5 KB
- references/claude-md-template.md 3.3 KB
- references/daily-curation-automation.md 3.1 KB
- references/inbox-readme-template.md 1.9 KB
- references/ingest-formats.md 7.6 KB
- references/ingest-ignore-defaults.md 1.8 KB
- references/obsidian-scaffolding.md 2.9 KB
- references/providers.yaml 144 KB
- references/tools-readme-template.md 3.3 KB
- references/wiki-archive-template.html 3.9 KB
- references/wiki-article-template.md 2.9 KB
- references/wiki-dashboard-template.html 5.9 KB
- references/wiki-deep-improve-report-template.html 6.2 KB
- references/wiki-gaps-template.md 717 B
- references/wiki-index-template.md 1.4 KB
- references/wiki-protocol.md 43 KB
- references/wiki-raw-template.md 310 B
- references/wiki-worklog-template.md 2.1 KB
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 · 302 lines · 94 tokens per session scan B 71f94b665a8c
harness is a skill published in the GitHub repository ericrisco/rsc-harness (65 stars, last pushed today), licensed MIT. It adds 94 tokens to every session and 6,005 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
confluence
Operational skill for Confluence: spaces, page trees, macros, labels, permissions, and REST content updates.
moai-workflow-spec
SPEC workflow orchestration with EARS format requirements, acceptance criteria, and Plan-Run-Sync integration for MoAI-ADK development. Use when creating SPEC documents or defining acceptance criteria.
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
starting-a-new-project
Use when the workspace is empty — no code yet — and the user brings a raw idea: the brand-new branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for features in an existing project — use brainstorming instead.
moai-workflow-templates
Template management system for code boilerplates, feedback templates, scaffolding, and project optimization workflows. Use when creating templates, generating boilerplate files, or managing scaffolding.