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 jeffreytse/grimoire-core --skill write-job-descriptiongit clone --depth 1 https://github.com/jeffreytse/grimoire-coreWrote 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/jeffreytse/grimoire-core/write-job-description)<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/write-job-description"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/write-job-description.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.00023 | $0.00891 |
| Opus 5 | $0.00012 | $0.00445 |
| Sonnet 5 | $0.00005 | $0.00178 |
| Haiku 4.5 | $0.00002 | $0.00089 |
Grade A, and why
write-job-description 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Job Description
Craft a clear, inclusive job description that attracts qualified candidates and sets accurate role expectations.
Why This Is Best Practice
Adopted by: Google, LinkedIn, Salesforce, Airbnb, and organizations using structured hiring Impact: LinkedIn data shows job postings with clear requirements receive 14% more applications; postings with inclusive language attract 42% more applicants from underrepresented groups. SHRM reports unclear JDs are a top cause of mis-hires, which cost 50–200% of annual salary. Why best: Structured JDs reduce bias in screening by focusing on observable skills over proxies (degree requirements), and clearly defined responsibilities reduce early attrition caused by expectation mismatch.
Sources: SHRM Job Description Writing Guide (2022); O*NET OnLine (US DOL); LinkedIn "Global Talent Trends" (2023)
Steps
-
Gather role inputs — interview the hiring manager on: daily responsibilities, success metrics at 90 days/1 year, top 3 must-have skills, team structure, and growth trajectory.
-
Write a compelling job title — use standard market titles (search O*NET or LinkedIn for benchmarks). Avoid internal jargon (e.g., "Ninja," "Rockstar," "Level 4 Associate II").
-
Draft the role summary — 2–4 sentences covering: what the team does, what this role owns, and why it matters. Lead with impact, not org chart position.
-
List key responsibilities — use 5–8 bullet points starting with action verbs (design, own, lead, analyze). Order by time allocation (most frequent first). Avoid laundry lists of 20+ items.
-
Define requirements — separate must-haves (minimum qualifications) from nice-to-haves (preferred). Audit each requirement: is a degree truly required, or is equivalent experience acceptable? Eliminate credential inflation.
-
Add compensation range — include salary band and equity/bonus structure. Postings with salary transparency receive 30% more applications (LinkedIn 2023). Required by law in many jurisdictions.
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 · 63 lines · 23 tokens per session scan A 6da09a6bb7b4
write-job-description is a skill published in the GitHub repository jeffreytse/grimoire-core (4 stars, last pushed 20d ago), licensed MIT. It adds 23 tokens to every session and 891 once invoked, about $0.0001 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
org-report
Generate an executive organization brief (leadership chain, direct reports, extended teams, and vendor partners) for a target person. Produces a Word + PDF report from a directory MCP source (WorkIQ is the reference implementation) and displays it in a Copilot canvas. Triggers on "generate org report for X", "build…
meeting-efficiency
Agenda design, time boxing, decision capture, async alternatives, and productive facilitation.
coaching-techniques
GROW model, active listening, developmental feedback, and team growth approaches.
stakeholder-management
Influence mapping, communication strategies, and expectation management for complex organizations.
business-analysis
Patterns for requirements elicitation, BRDs, process analysis, and stakeholder alignment.
scaffolding-generator
Pattern-aware code scaffolding that detects existing conventions and generates new components matching the codebase style. Use when asked to "scaffold a component", "generate boilerplate", "create a new module", "bootstrap a service", "add a new endpoint", "create a new controller", or "add a new feature module".…