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 w95/awesome-claude-corporate-skills --skill job-description-writergit clone --depth 1 https://github.com/w95/awesome-claude-corporate-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/w95/awesome-claude-corporate-skills/job-description-writer)<a href="https://agentmods.dev/skills/w95/awesome-claude-corporate-skills/job-description-writer"><img src="https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-skills/job-description-writer/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/w95/awesome-claude-corporate-skills/job-description-writer"><img src="https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-skills/job-description-writer.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.00061 | $0.02394 |
| Opus 5 | $0.00030 | $0.01197 |
| Sonnet 5 | $0.00012 | $0.00479 |
| Haiku 4.5 | $0.00006 | $0.00239 |
Grade A, and why
job-description-writer 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 9d 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Job Description Writer
Overview
This skill helps HR professionals and hiring managers create effective, inclusive job descriptions that attract diverse talent, clearly communicate role expectations, and support equitable hiring processes. It ensures JDs include comprehensive role details, transparent compensation guidance, DEI language, and compliance-ready structure.
When to Use This Skill
- Creating new job descriptions for open positions
- Revising existing JDs to be more inclusive or accurate
- Developing hiring briefs for recruiter guidance
- Standardizing JD format across the organization
- Adding salary transparency and DEI elements to existing descriptions
- Ensuring JDs comply with accessibility and non-discrimination standards
- Creating role family templates for similar positions
Key Components
1. Core Structure Template
A well-organized JD should follow this proven framework:
- Position Title - Use inclusive, searchable language
- Department & Reporting Line - Clear organizational context
- Position Summary - 2-3 sentence overview of purpose
- Key Responsibilities - 5-8 main duties with impact metrics
- Required Qualifications - Only non-negotiable requirements (avoid "nice-to-haves")
- Preferred Qualifications - Open doors for diverse candidates
- Compensation & Benefits - Transparent salary bands, benefits overview
- Company Culture/DEI Statement - Commitment to inclusion
- Application Instructions - Accessibility accommodations offered
2. Inclusive Language Practices
- Replace "native English speaker" with "fluent in English"
- Use "years of experience" instead of "young and energetic"
- Avoid gendered terms (use "salesperson" not "salesman")
- Include "and more" in job duties to signal flexibility
- Emphasize "equivalent experience" to accept diverse backgrounds
- Replace ageist language (avoid "digital native," "rockstar," "ninja")
- Use "we encourage applications from underrepresented groups"
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.
- 9d ago First seen · 239 lines · 61 tokens per session scan A 10d918d77b69
job-description-writer is a skill published in the GitHub repository w95/awesome-claude-corporate-skills (198 stars, last pushed 6mo ago), licensed MIT. It adds 61 tokens to every session and 2,394 once invoked, about $0.0003 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
workflow
Starts and manages autonomous agent workflows. Triggers: workflow, start workflow, autonomous agents, agent pipeline.
autonomous-dev
Drives a brief, specification, issue or existing PR through implementation, review, tests and QA to a ready PR. Persists ownership, progress and commit-bound evidence for safe resumption. Use for autonomous software delivery or finishing an interrupted development run.
onboard
Sets up ai-toolkit in a project: symlinks, CLAUDE.md, intent interview. Triggers: onboard, setup project, install ai-toolkit, migrate project.
plan
Breaks features/goals into phased plans with task lists, agent assignments, dependencies. Triggers: plan feature, implementation roadmap, break down task, project phases.
prd-to-issues
Splits a PRD into vertical-slice GitHub issues with HITL/AFK tagging and dependencies. Triggers: PRD to issues, create tickets, break down PRD, work items.
prd-to-plan
Converts PRD into phased plan via tracer-bullet vertical slices. Triggers: PRD to plan, break down PRD, implementation plan, tracer bullets, phased plan.