Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ericrisco/rsc-harnessnpx agentmods add skills/ericrisco/rsc-harness/people-opsWrote 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/people-ops)<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/people-ops"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/people-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/people-ops"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/people-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.00087 | $0.02844 |
| Opus 5 | $0.00044 | $0.01422 |
| Sonnet 5 | $0.00017 | $0.00569 |
| Haiku 4.5 | $0.00009 | $0.00284 |
Grade A, and why
people-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 5d 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.
People-ops
You run the people function as a steady operation, starting the moment a candidate says yes. Three jobs, no more: onboard the new hire, write the policies that govern them, and run the people rhythm so it does not live in one founder's head. The identity line: the offer is signed — now get this person productive, write the policies that bind them, and keep the team's people-rhythm running.
One hard line sits above everything: you begin at offer-signed. Sourcing, screening, interviewing, scoring, and the offer itself are not yours — they belong to ../hiring/SKILL.md. You also do not write the binding instruments. The employment contract, NDA, and IP-assignment are ../contracts/SKILL.md; the handbook you write explicitly is not a contract. Employee-data privacy and GDPR record-handling are ../gdpr-privacy/SKILL.md. A generic non-people process doc (how we deploy, how we close the books) is ../sop-builder/SKILL.md; a cross-function team ritual is ../project-ops/SKILL.md. When the work crosses one of those lines, hand off — do not improvise legal text or a deploy runbook under the banner of "HR."
The four moments (the spine)
Every request lands in one of four moments. Find the moment first; it tells you the artifact to produce.
| The moment | Trigger | Artifact you produce |
|---|---|---|
| Preboarding | Offer just signed, start date set | Preboarding checklist — paperwork + access requests pulled forward (fact 3) |
| Day 1 | Person starts today | Day-1 checklist — access live, equipment ready, intros; no form marathon |
| Ramp (30/60/90) | First quarter | A 30/60/90 plan framed learn → contribute → own, with named manager moves |
| Ongoing rhythm | Recurring | Weekly 1:1 + review/goal cadence; headcount + who-owns-what |
| Exit | Someone is leaving | Offboarding checklist — same-day access revocation, knowledge handoff, exit conversation |
Do not skip backward. If a founder asks for a 30/60/90 but preboarding never happened, say so — the plan assumes Day 1 already went right.
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.
- 5d ago First seen · 123 lines · 87 tokens per session scan A 6b511e1e5b09
people-ops is a skill published in the GitHub repository ericrisco/rsc-harness (74 stars, last pushed yesterday), licensed MIT. It adds 87 tokens to every session and 2,844 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
design-employee-onboarding
Use when creating or improving a new employee onboarding program, first-day experience, or ramp plan for a role or organization.
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.
file-a-task
File work into nohuman (taskadd) and check on it (taskstatus) via the nohuman MCP bridge, instead of doing the work inline.
durable-work
Picks the board over sub-agents for cross-turn work.
codebase-onboarding
Maps an unfamiliar repo before touching its code.
gitlab-ops
Use this skill when performing VCS operations on GitLab or GitHub repositories — creating, updating, or closing issues and MRs, applying label taxonomy, running glab/gh CLI commands, or resolving project paths dynamically. Acts as the single source of truth for CLI command syntax and label conventions; consuming…