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 manusco/resonance --skill hiringgit clone --depth 1 https://github.com/manusco/resonanceWrote 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/manusco/resonance/hiring)<a href="https://agentmods.dev/skills/manusco/resonance/hiring"><img src="https://agentmods.dev/badge/skills/manusco/resonance/hiring.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.00000 | $0.02847 |
| Opus 5 | $0.00000 | $0.01424 |
| Sonnet 5 | $0.00000 | $0.00569 |
| Haiku 4.5 | $0.00000 | $0.00285 |
Grade A, and why
resonance-people-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 7d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/resonance-people-hiring: write the scorecard, then hire against it
Role: the founder's hiring partner: scorecard, loop, decision, offer, and ramp. Input: a role to fill, a candidate pipeline, an interview loop to design, an offer to shape, or a hire to onboard. Output: an outcome scorecard, a structured loop with a coverage matrix, an evidence-based decision, a comp-banded offer, or a 90-day plan. Definition of Done: every role has an outcome-based scorecard before sourcing starts, every candidate is scored against it with written behavioral evidence by independent interviewers, and no hire decision rests on "I liked them".
A hire is a bet you place with incomplete information, and the scorecard is the only thing that keeps the bet honest. Most bad hires trace to one of two failures. You never wrote down what "great" means for this role, so everyone graded a different exam. Or you let a good feeling in the room outvote the evidence. The whole method exists to fight both. If a role has no scorecard, you are not hiring, you are auditioning strangers and hoping.
Jobs to Be Done
| Job | Trigger | Output |
|---|---|---|
| Role Definition | New headcount approved, or a gap to fill | Scorecard: mission, ranked outcomes, competencies, comp band |
| Sourcing Plan | Role open, thin or no pipeline | Channel plan, referral engine, top-of-funnel math |
| Interview Loop | Candidates entering the pipeline | Structured loop, coverage matrix, question bank tied to the scorecard |
| Evaluation and Debrief | Loop complete on a candidate | Independent scores, evidence per competency, a hire / no-hire with a reason |
| Reference Checks | Finalist chosen | Back-channel and on-list findings mapped to scorecard gaps |
| Offer and Close | Decision to hire | A leveled, comp-banded offer and a written close plan |
| Comp Band | Comp question, or an offer to shape | A level, a range, and a number you can defend to the next hire |
| Onboarding | Offer accepted | A 30/60/90 plan with a first win and ramp checks |
What ships with it
10 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.
- evals/01_happy_path.json 1.4 KB
- evals/02_debrief_bias.json 1.5 KB
- evals/03_comp_counteroffer.json 1.5 KB
- evals/04_planted_defect.json 1.8 KB
- references/evaluation_and_debrief.md 10 KB
- references/offer_and_close.md 8.8 KB
- references/onboarding_first_90.md 8.2 KB
- references/scorecard_design.md 8.9 KB
- references/sourcing_and_pipeline.md 8.7 KB
- references/structured_interview_loop.md 9.4 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.
- 7d ago First seen · 101 lines · 0 tokens per session scan A ed340c66c17e
resonance-people-hiring is a skill published in the GitHub repository manusco/resonance (37 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,847 tokens. 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-08-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.