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 hiringgit 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/hiring)<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/hiring"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/hiring.svg" alt="Measured on agentmods" 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.02840 |
| Opus 5 | $0.00041 | $0.01420 |
| Sonnet 5 | $0.00016 | $0.00568 |
| Haiku 4.5 | $0.00008 | $0.00284 |
Grade A, and why
hiring 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 4d 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hiring
You run the selection funnel up to the hire decision: write the post, screen the pile, structure the loop, and score candidates so the call is evidence-based and defensible. The product of this skill is a job post, a set of screen decisions, an interview structure, and a scorecard that says Hire / On-Hold / No-Hire with the reason written down.
Hard boundary: the moment the offer is accepted, you are done. Onboarding,
payroll, equipment, performance reviews, PTO — that is ../people-ops/SKILL.md.
Do not draft offer-letter terms here either; that is ../contracts/SKILL.md.
The funnel (the spine)
Every engagement walks this line, in order. Do not skip to scoring before the rubric exists.
define role → write post → screen pile → structured loop → independent scores → calibrated debrief → decision
One rule per stage, with the why:
- Define the role first. You cannot screen against criteria you have not named. Write the 3–6 competencies before the post, because they drive the post, the questions, and the scorecard.
- Write the post from the competencies. A post is the competencies turned outward, not a wish list.
- Screen against one rubric. Same criteria, same order, every candidate, or the comparison is meaningless.
- Run a structured loop. Same questions, same rubric, every candidate — structured interviews are the single highest-validity selection method (~.51 predictive validity vs ~.38 unstructured; the 2022 Sackett et al. re-analysis ranks them above cognitive-ability tests). Unstructured = lottery.
- Score independently, then calibrate. Each interviewer submits before the group talks. Debrief is calibration, not a re-vote.
Write the job post
The job post is the top of the funnel and it leaks candidates if you write it
wrong. Apply the company voice from ../brand-voice/SKILL.md if one exists — but
do not author the voice guide here, just apply it.
Split must-haves from nice-to-haves, and keep must-haves short. Women tend to apply only when they meet ~100% of listed requirements vs ~60% for men, so every extra "requirement" silently filters out qualified candidates. Cap must-haves at ~6. Everything that is genuinely learnable on the job goes under nice-to-have.
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.
- 4d ago First seen · 237 lines · 82 tokens per session scan A b48c3657a227
hiring is a skill published in the GitHub repository ericrisco/rsc-harness (70 stars, last pushed today), licensed MIT. It adds 82 tokens to every session and 2,840 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
performing-soc2-type2-audit-preparation
Automates SOC 2 Type II audit preparation including gap assessment against AICPA Trust Services Criteria (CC1-CC9), evidence collection from cloud providers and identity systems, control testing validation, remediation tracking, and continuous compliance monitoring. Covers all five TSC categories (Security…
merge-aliases
Folds two surface names for the same backend system into one canonical entity, keeping every original mention individually retrievable, and refuses to merge pairs that only share spelling.
anchor-and-lock
Consults a check that sits outside the loop system before finalizing any decision the frozen facts bear on, and refuses every attempt by a loop to rewrite a node marked frozen, regardless of how convergent the loop's own reasoning looks.
counter-metric-check
Compares a watched loop's headline reading against an independently owned counter-metric reading for each period in a governance graph, and produces a governance edge for every period where the counter-metric crosses its recorded ceiling.
traverse-multi-hop
Expresses a multi-hop lineage question as a single variable-length path match against native graph storage, bounded by an explicit hop depth and an explicit relationship-type allowlist, instead of a recursive relational join that grows one level per hop.
query-graph
Loads schema.sql into a local SQLite file, then answers availability and provenance questions against the nodes/edges tables with real SQL instead of re-reading source material.