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 agentmods add skills/hoavdc/codexkit/codexkit-job-description-writernpx skills add hoavdc/CodexKit --skill codexkit-job-description-writergit clone --depth 1 https://github.com/hoavdc/CodexKitWrote 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/hoavdc/codexkit/codexkit-job-description-writer)<a href="https://agentmods.dev/skills/hoavdc/codexkit/codexkit-job-description-writer"><img src="https://agentmods.dev/badge/skills/hoavdc/codexkit/codexkit-job-description-writer.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 | $0.00066 | $0.00949 |
| Opus 5 | $0.00033 | $0.00475 |
| Sonnet 5 | $0.00013 | $0.00190 |
| Haiku 4.5 | $0.00007 | $0.00095 |
Grade A, and why
codexkit-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 3d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Job Description Writer
Purpose
Create compelling, accurate job descriptions that attract the right candidates by clearly communicating the role, requirements, and employer value proposition.
When to use
- opening a new position and need a JD from scratch
- updating outdated job descriptions
- standardizing JD format across the organization
- creating localized JDs for different markets
When not to use
- defining career levels or promotion criteria
- writing performance review criteria
- creating training curricula
Inputs
- job title and level (junior / mid / senior / lead / director)
- department and reporting line
- key responsibilities (rough list is fine)
- must-have vs nice-to-have qualifications
- employment type (full-time, part-time, contract, remote)
- salary range or band (optional but recommended)
- company culture keywords or employer brand tone
- industry and location
Procedure
- Write the role summary (2–3 sentences):
- What the role does, who it reports to, and why it matters
- Focus on impact, not just activities
- Define key responsibilities (5–8 bullet points):
- Start each with an action verb
- Order by importance, not alphabetically
- Be specific: "Design and launch 3 marketing campaigns per quarter" not "manage marketing"
- List qualifications in two tiers:
- Must-have (hard requirements) — be honest, don't inflate
- Nice-to-have (preferred but not required) — keeps the pool open
- Include SHRM competency alignment where applicable:
- Technical competency: domain knowledge required
- Behavioral competency: communication, leadership, analytical thinking
- Write the EVP section (Employer Value Proposition):
- What the company offers beyond salary
- Growth opportunities, culture, benefits, mission
- Add practical details:
- Location (or remote policy), travel requirements
- Salary range (if applicable — improves candidate quality)
- Application instructions and timeline
- Inclusive language check:
- Remove gendered language
- Avoid unnecessary degree requirements
- Flag biased phrases (e.g., "rockstar", "ninja", "young and dynamic")
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 111 lines · 66 tokens per session scan A d3990ef02ab6
codexkit-job-description-writer is a skill published in the GitHub repository hoavdc/CodexKit (21 stars, last pushed 3mo ago), licensed MIT. It adds 66 tokens to every session and 949 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-08-30.
Other skills, from other repositories
reducing-aigc-detection
Systematically reduce AIGC detection rates in academic papers (Chinese/English). Analyzes detection reports, identifies high-impact sections, applies multi-layer rewriting strategies preserving formatting/footnotes, and verifies results. Supports 维普/知网/Turnitin platforms.
architecting-security
安全架构与治理：威胁建模 (STRIDE/PASTA/LINDDUN)、零信任身份架构、IAM/SSO/MFA/PAM、合规框架 (SOC2/PCI/HIPAA/GDPR)、DLP、隐私工程、安全控制设计。Use when designing security architecture, threat modeling new systems, implementing zero-trust identity, designing IAM/SSO/PAM, building compliance evidence chains, or planning privacy-by-design.
defending-applications
Application security defense knowledge for builders. Covers Web/API/GraphQL hardening (XSS/SQLi/SSRF/IDOR/BOLA/Mass Assignment/deserialization/upload/path traversal), authentication/authorization (OAuth 2.0/OIDC/JWT/Session/Cookie/SAML/SSO), and LLM application security (prompt injection, jailbreak, RAG poisoning…
detecting-and-responding
蓝队与紫队工程：检测规则编写、SIEM/EDR 调优、事件响应、数字取证、威胁狩猎、ATT&CK 映射、紫队演练闭环。Use when writing Sigma/YARA detection rules, tuning SIEM noise, responding to security incidents, conducting forensic analysis, hunting threats, or running purple team exercises.
securing-cloud-and-supply-chain
云原生与软件供应链安全防御。容器/K8s 加固、Service Mesh、CI/CD 安全、SLSA/SBOM/Sigstore、云 IAM、Secrets 管理、IaC 安全。Use when hardening Kubernetes clusters, auditing CI/CD pipelines, implementing supply chain security, managing cloud IAM, or reviewing IaC code.
analyzing-changes
Analyzes code changes, detects documentation drift, and evaluates change impact scope. Use when reviewing diffs, checking doc sync, or running pre-commit analysis. Automatically triggered after design-level changes or refactoring.