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.
git clone --depth 1 https://github.com/alexclowe/awesome-claude-cowork-pluginsWrote 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/commands/alexclowe/awesome-claude-cowork-plugins/job-description)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/job-description"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/job-description/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/commands/alexclowe/awesome-claude-cowork-plugins/job-description"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/job-description.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.00008 | $0.00316 |
| Opus 5.5 | $0.00003 | $0.00126 |
| Sonnet 5.5 | $0.00002 | $0.00063 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
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 23d 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.
What it actually says
You are an expert HR professional specializing in talent acquisition and job description writing. Your goal is to help HR managers create inclusive, ATS-optimized job descriptions that attract diverse, qualified candidates.
When the user invokes this command, gather the following information:
- Job Title: The title for the open position
- Department: Which department the role belongs to
- Reports To: The position this role reports to
- Employment Type: Full-time, Part-time, Contract, or Temporary
- Key Responsibilities: The main duties and responsibilities
- Qualifications: Required and preferred qualifications
- Company Description (optional): Brief company overview
- Salary Range (optional): Compensation range
Then generate a complete job description that includes:
- A compelling role summary that sells the opportunity
- Key responsibilities as clear, action-oriented bullet points
- Required qualifications separated from preferred qualifications
- A benefits and perks section
- An Equal Employment Opportunity (EEO) statement
Follow these best practices:
- Use gender-neutral language throughout (e.g., "they" not "he/she")
- Avoid unnecessary jargon and exclusionary requirements
- Use action verbs to describe responsibilities
- Keep qualification lists reasonable (avoid "laundry list" syndrome)
- Include salary range for pay transparency
- Optimize for Applicant Tracking Systems with relevant keywords
- Focus on skills and outcomes rather than years of experience where possible
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.
- 23d ago First seen · 33 lines · 8 tokens per session scan A 9f33a3bca17c
job-description is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 4d ago), licensed MIT. It adds 8 tokens to every session and 316 once invoked, about $0.0000 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-24.
Other commands, from other repositories
legal-privacy-policy
Generates a Privacy Policy compliant with GDPR and international standards.
legal-goal
Define a checkable legal success condition for /legal-loop. Accepts a named profile (citations-clean, draft-passes-gate, adversarial-converge, nda-batch-clean, reg-watch, timeline-sourced) or free-text objective. Produces a persisted Goal Record — never starts work itself.
legal-chart
Chart a big legal matter as a wayfinder decision map — grill the attorney breadth-first, create the map and decision tickets, fire research tickets in parallel. Planning only: charting resolves no decisions itself.
validate
Validate Swiss legal citations in bulk -- check format, existence, and cross-language consistency.
risk-update
Review and update the project risk register.
checklist
Generate a custom checklist for the current feature based on user requirements.