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 T4LEL/Claude-Arsenal --skill hiregit clone --depth 1 https://github.com/T4LEL/Claude-ArsenalWrote 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/t4lel/claude-arsenal/hire)<a href="https://agentmods.dev/skills/t4lel/claude-arsenal/hire"><img src="https://agentmods.dev/badge/skills/t4lel/claude-arsenal/hire/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/t4lel/claude-arsenal/hire"><img src="https://agentmods.dev/badge/skills/t4lel/claude-arsenal/hire.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.00039 | $0.00781 |
| Opus 5 | $0.00019 | $0.00391 |
| Sonnet 5 | $0.00008 | $0.00156 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
hire 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 10d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hire
Scorecard before job description, job description before interviews — skip the scorecard and you hire whoever interviews best, not whoever does the job.
Copy this checklist and check off items as you complete them:
Hire Progress:
- [ ] Step 1: Scorecard
- [ ] Step 2: JD draft
- [ ] Step 3: Sourcing plan
- [ ] Step 4: Interview loop
- [ ] Step 5: Contract checklist
- [ ] Report
Step 1 — Scorecard before JD
Define the outcome, not the resume. Write 3-5 measurable outcomes for what great looks like at the 90-day mark (shipped what, moved which metric by how much), plus two skill lists: required and nice-to-have. If the role's scope is fuzzy — generalist or specialist, contract or full-time, needed now or in three months — delegate to the biz-strategist agent with the business problem this hire is meant to solve.
Step 2 — JD draft
Delegate to the copywriter agent with the scorecard as input, not a blank prompt. The JD leads with the 90-day outcomes, states the stack plainly (the actual tools, not a wishlist of 15 technologies nobody uses together), and states a real compensation range — one you'd defend out loud in the interview, not a placeholder. Publishing the JD anywhere public is outward-facing: confirm with the user before posting it.
Step 3 — Sourcing plan
Rank channels for this specific role type — relevant communities, job boards, freelance platforms (Upwork/Toptal for contract work, LinkedIn for full-time), personal network — and commit to the top 2-3 rather than spraying across all of them. Name the first 3 concrete actions (post in which community, DM which 5 people, apply which platform filter) with who does each and by when.
Step 4 — Interview loop
Identical loop for every candidate — that's what makes them comparable:
- 30-minute screen: motivation for this specific role, walkthrough of relevant past work.
- PAID, timeboxed work sample pulled from the real backlog — an actual ticket or task, not a synthetic puzzle. Pay it whether or not the candidate advances.
- Score against the Step 1 scorecard with a rubric — required skills as line items, not gut feel.
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.
- 10d ago First seen · 57 lines · 39 tokens per session scan A e20761b3b91e
hire is a skill published in the GitHub repository T4LEL/Claude-Arsenal (1 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 781 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
workers-best-practices
Cloudflare Workers best practices for production applications. Use when writing, reviewing, or configuring Workers.
find-journalists
Build, refine, dedupe, and enrich small fit-checked journalist lists for newsjack campaigns. Uses the newsjack CLI (preferred) or the medialyst MCP for news search and journalist enrichment, and falls back to a best-effort local mode with no verified contacts; the agent owns how returned data is organized.
story-origin-check
Recover the first public timestamp and canonical major coverage for a newsjacking signal, then decide whether newer coverage is the same story, a different story, or a materially new development.
relevance-coarse-filter
Cheap, high-recall first-pass filter that removes obvious junk from a detector candidate pool before expensive story-origin research and PR judgment. Decides keep, monitoronly, or reject — never ranks, writes angles, verifies dates, or decides whether to pitch.
annotating-task-lineage
Annotate Airflow tasks with data lineage using inlets and outlets. Use when the user wants to add lineage metadata to tasks, specify input/output datasets, or enable lineage tracking for operators without built-in OpenLineage extraction.
aws-cloudformation-cloudfront
Provides AWS CloudFormation patterns for CloudFront distributions, origins (ALB, S3, Lambda@Edge, VPC Origins), CacheBehaviors, Functions, SecurityHeaders, parameters, Outputs and cross-stack references. Use when creating CloudFront distributions with CloudFormation, configuring multiple origins, implementing caching…