ResumeSkills is a collection of AI-agent skills for improving resumes, preparing job applications, practicing interviews, and planning career moves. It is intended for job seekers, career changers, and professionals using Claude Code for tasks such as ATS checks, job-description matching, resume tailoring, and salary negotiation. The catalogue entry consists of the project's career-focused skills.
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/paramchoudhary/resumeskills/reference-list-buildernpx skills add Paramchoudhary/ResumeSkills --skill reference-list-buildergit clone --depth 1 https://github.com/Paramchoudhary/ResumeSkillsWrote 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/paramchoudhary/resumeskills/reference-list-builder)<a href="https://agentmods.dev/skills/paramchoudhary/resumeskills/reference-list-builder"><img src="https://agentmods.dev/badge/skills/paramchoudhary/resumeskills/reference-list-builder.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.00012 | $0.01907 |
| Opus 5 | $0.00006 | $0.00954 |
| Sonnet 5 | $0.00002 | $0.00381 |
| Haiku 4.5 | $0.00001 | $0.00191 |
Grade A, and why
reference-list-builder 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 5d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- reference-list-builder — 100% identical, 0 lines differ
- reference-list-builder — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reference List Builder
When to Use This Skill
Use this skill when the user:
- Needs to create a professional reference list
- Wants help choosing the right references
- Needs to format references properly
- Is preparing references for job applications
- Mentions: "references", "reference list", "professional references", "reference check"
Core Capabilities
- Format professional reference lists
- Guide reference selection strategy
- Prepare reference briefing materials
- Anticipate reference check questions
- Handle difficult reference situations
- Coordinate reference outreach
Reference Strategy
Who Makes a Good Reference?
Ideal References:
- Former direct managers (most important)
- Senior colleagues who observed your work
- Cross-functional partners
- Clients or customers
- Direct reports (for leadership roles)
- Professors or advisors (for recent graduates)
Reference Hierarchy:
- Most Valuable: Recent direct supervisor
- Very Valuable: Senior leaders who know your work
- Valuable: Peers and cross-functional partners
- Acceptable: Clients, vendors, professors
- Avoid: Friends, family, HR contacts only
Who to Avoid
- ❌ Current employer (without permission)
- ❌ People who barely know you
- ❌ References from 10+ years ago only
- ❌ Personal friends (unless specified)
- ❌ People who might give lukewarm feedback
- ❌ Anyone you haven't contacted in advance
Reference List Format
Standard Format
PROFESSIONAL REFERENCES
Jane Smith
Senior Director of Product
TechCorp Inc.
Phone: (555) 123-4567
Email: [email protected]
Relationship: Direct supervisor for 3 years (2020-2023)
John Doe
VP of Engineering
Previous Company
Phone: (555) 234-5678
Email: [email protected]
Relationship: Cross-functional partner on 5 major projects
Information to Include
Required:
- Full name
- Current job title
- Current company
- Phone number
- Professional email
- Your relationship to them
Optional:
- LinkedIn URL
- Best time to reach
- Preferred contact method
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.
- 5d ago First seen · 348 lines · 12 tokens per session scan A ef4d07942777
reference-list-builder is a skill published in the GitHub repository Paramchoudhary/ResumeSkills (2,093 stars, last pushed 2mo ago), licensed MIT. It adds 12 tokens to every session and 1,907 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…