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 SkillMedev/skills --skill hiring-a-players-and-sopsgit clone --depth 1 https://github.com/SkillMedev/skillsWrote 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/skillmedev/skills/hiring-a-players-and-sops)<a href="https://agentmods.dev/skills/skillmedev/skills/hiring-a-players-and-sops"><img src="https://agentmods.dev/badge/skills/skillmedev/skills/hiring-a-players-and-sops/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/skillmedev/skills/hiring-a-players-and-sops"><img src="https://agentmods.dev/badge/skills/skillmedev/skills/hiring-a-players-and-sops.svg" alt="Reviewed on agentmods" width="80" 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.00126 | $0.02335 |
| Opus 5.5 | $0.00050 | $0.00934 |
| Sonnet 5.5 | $0.00025 | $0.00467 |
| Haiku 4.5 | $0.00013 | $0.00233 |
Grade A, and why
hiring-a-players-and-sops 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 1mo 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hiring A-Players and SOPs
A gym stops scaling when the owner is the bottleneck. Run a role-outcome hiring funnel that finds people who produce results without supervision, and a four-step method that turns the owner's knowledge into SOPs someone else can run.
Workflow
Pick the entry point: if the owner is drowning in operations, start at Step 5 (SOPs). If growth is capped by the owner's own selling or coaching hours, start at Step 1 (hiring).
Step 1: Sequence the hire before defining it
A scaling single-location gym hires in this order:
- Sales setter or salesperson first - book and close so the owner stops being the only seller. Frees the most owner time and funds the next hire.
- Coach next - deliver sessions as the member base grows, protecting retention.
- Manager last - own the daily operation and the scoreboard so the owner can step out of the seat.
Name which role you are hiring now and why it is next.
Step 2: Define the role by its outcome, not a task list
A task list attracts task-doers; an outcome attracts people who want to win. Fill the role-scorecard before posting anything:
- Mission: one line stating what this role is responsible for producing.
- Outcomes with numbers: success at 90 days and 12 months (e.g. "book 60 consults/mo at 70% show rate").
- Competencies: only the few that actually predict success in that outcome.
Step 3: Run a volume-based candidate funnel
Hiring is a funnel like lead generation - more candidates at the top means a better hire at the bottom.
- Source widely: job boards, your member base, referrals, local networks. Aim for many applicants.
- Screen fast: a short application plus one or two knockout questions.
- Use a work sample: finalists do the actual work - a setter runs a mock booking call, a coach runs a real session, a manager fixes a broken process on paper. Work samples predict performance far better than interviews.
See references/hiring-funnel for sourcing and screening detail.
Step 4: Pay top of market and decide on cost per result
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.
- 1mo ago First seen · 192 lines · 126 tokens per session scan A a5723090deeb
hiring-a-players-and-sops is a skill published in the GitHub repository SkillMedev/skills (19 stars, last pushed 3d ago), licensed MIT. It adds 126 tokens to every session and 2,335 once invoked, about $0.0005 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
feature-prioritisation
Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…
design-handoff-brief
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…
contact-cache
Track all identified/contacted people across strategies. CSV-backed contact database with dedup by LinkedIn URL or email. Prevents duplicate outreach when running strategies on a recurring cadence.
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…
ai-assisted-performance-review
Evaluate performance fairly when output is AI-assisted — what still measures the human, what now measures the tooling, and how to run the review conversation. Use when reviewing someone whose work is heavily AI-assisted, when output volume stopped meaning anything, when calibrating a team with uneven AI adoption, or…
role-redesign-for-ai
Redesign a job role that AI now does a large part of — deliberately, instead of quietly expecting the same headcount to absorb 140% output. Use when AI has changed what a role spends time on, when writing a revised role charter or job description post-AI, when a team asks 'what is my job now', or when planning…