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/latestaiagents/agent-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/commands/latestaiagents/agent-skills/write-job-description)<a href="https://agentmods.dev/commands/latestaiagents/agent-skills/write-job-description"><img src="https://agentmods.dev/badge/commands/latestaiagents/agent-skills/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.00010 | $0.00367 |
| Opus 5 | $0.00005 | $0.00183 |
| Sonnet 5 | $0.00002 | $0.00073 |
| Haiku 4.5 | $0.00001 | $0.00037 |
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 4d 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
/write-job-description
Create a professional job description that attracts diverse talent.
What I Need
Tell me:
- What role are you hiring for?
- What level (junior, mid, senior, lead)?
- What team/department?
- Key responsibilities (top 3-5)
- Must-have vs nice-to-have skills
- Salary range (if sharing)
- Remote/hybrid/on-site?
What I'll Create
A complete job description with:
- Compelling intro - Why this role matters
- Clear responsibilities - Action-oriented, outcome-focused
- Realistic requirements - Separated into must-have and nice-to-have
- Inclusive language - Checked for bias
- Benefits highlights - What you offer
- Company snapshot - Brief culture description
Output Format
# [Role Title]
## About the Role
[Impact-focused summary]
## What You'll Do
- [Responsibility 1]
- [Responsibility 2]
...
## What You'll Bring
**Required:**
- [Must-have 1]
...
**Nice to Have:**
- [Preferred 1]
...
## What We Offer
[Compensation and benefits]
## About Us
[Company description]
Inclusivity Checks
I'll automatically check for:
- Gendered language
- Unnecessary requirements
- Age-coded phrases
- Jargon that excludes
Example
You: /write-job-description
Role: Senior Product Manager
Team: Growth
Remote: Hybrid (3 days office)
Key: Drive user acquisition, work with eng/design, define roadmap
Claude: [Generates complete, inclusive JD]
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.
- 4d ago First seen · 80 lines · 10 tokens per session scan A f4793b0cf42e
write-job-description is a command published in the GitHub repository latestaiagents/agent-skills (5 stars, last pushed 4mo ago), licensed MIT. It adds 10 tokens to every session and 367 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 commands, from other repositories
fdk-react-create
Create a new Platform 3.0 React Meta app (default UI stack). Uses fdk create react-starter-template or react-meta skeletons with DEW components, metaConfig in manifest.json, and React Router.
fdk-refactor
Reduce function complexity in a Freshworks app to meet cyclomatic complexity ≤ 7 per function. Extracts helper functions, simplifies conditionals, and preserves behavior while improving code quality.
fw-setup-uninstall
Uninstall FDK completely — keeps Node.js and nvm (/fw-setup uninstall).
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.