Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jain777/jobclaw-skillsnpx agentmods add skills/jain777/jobclaw-skills/tailor-resumeWrote 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/jain777/jobclaw-skills/tailor-resume)<a href="https://agentmods.dev/skills/jain777/jobclaw-skills/tailor-resume"><img src="https://agentmods.dev/badge/skills/jain777/jobclaw-skills/tailor-resume/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/jain777/jobclaw-skills/tailor-resume"><img src="https://agentmods.dev/badge/skills/jain777/jobclaw-skills/tailor-resume.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.00081 | $0.02393 |
| Opus 5 | $0.00041 | $0.01196 |
| Sonnet 5 | $0.00016 | $0.00479 |
| Haiku 4.5 | $0.00008 | $0.00239 |
Grade A, and why
tailor-resume 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 12d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tailor-resume
Turn the master profile into a resume aimed at one job — maximizing relevance and ATS keyword match without inventing anything.
Inputs
- Profile: read
profile/master-profile.md(frontmatter + body, plus any[VERIFY]flags — don't rely on unverified facts). If missing →/build-profile. - Job: pasted description, URL, or an entry from
jobs/found-<date>.json. Known-info gate (RULES §6): if no job is given inline, readjobs/current.json— do not re-ask for the JD when score-fit/find-jobs already captured it. - (Optional)
scores/<job-id>.score.jsonfromscore-fit— reuse itsmissing_keywordslist.
The one hard rule
Never fabricate. You may select, reorder, reframe, and re-emphasize the user's real experience and use the job's vocabulary for things they actually did. You may not invent roles, titles, dates, metrics, skills, or tools they don't have. If a must-have is genuinely absent, leave it out and flag it to the user — don't paper over it.
Read but never quote: the context block
The profile has a context: block with career_goal and additional_info. Read both for signal — use them to bias which experience strand to lead with in the Summary and which skills to elevate. Never quote, paraphrase, or echo their contents into the Summary, bullets, or anywhere else the candidate would send out. Do not write phrases like "My career goal is…" — that signal stays internal.
Method
- Load region conventions. Read the target region's pack in
../../knowledge/regions/and follow its resume rules — length, what to include/omit (e.g., US: omit photo/DOB, no salary; IN: 1–2 pages, include notice period, drop photo/DOB by default), spelling variant, and date format. These govern the structure below. - Read the job for must-have keywords, responsibilities, seniority, and the language it uses.
- Select & order the profile's most relevant experience, skills, and projects for this role; drop or shorten the irrelevant. Use
context.career_goalas a tie-breaker on what to lead with. - Rewrite bullets under the rubric below.
- Surface keywords naturally into summary/skills/bullets — enough to pass ATS screening, never keyword-stuffed.
- Honor constraints/voice from the profile Notes (tone, hard limits).
- Self-check the draft against the rubric and anti-patterns before writing.
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.
- 12d ago First seen · 112 lines · 81 tokens per session scan A ebc2b672b459
tailor-resume is a skill published in the GitHub repository jain777/jobclaw-skills (5 stars, last pushed 3mo ago), licensed MIT. It adds 81 tokens to every session and 2,393 once invoked, about $0.0004 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…