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 skills add zszz3/AgentRecall --skill resume-optimizationgit clone --depth 1 https://github.com/zszz3/AgentRecallWrote 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/zszz3/agentrecall/resume-optimization)<a href="https://agentmods.dev/skills/zszz3/agentrecall/resume-optimization"><img src="https://agentmods.dev/badge/skills/zszz3/agentrecall/resume-optimization/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/zszz3/agentrecall/resume-optimization"><img src="https://agentmods.dev/badge/skills/zszz3/agentrecall/resume-optimization.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Agent Snooping · line 176 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
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.00045 | $0.01796 |
| Opus 5.5 | $0.00018 | $0.00718 |
| Sonnet 5.5 | $0.00009 | $0.00359 |
| Haiku 4.5 | $0.00005 | $0.00180 |
Grade A, and why
resume-optimization 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 1mo 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resume Optimization
Comprehensive guidance for creating effective software engineering resumes that pass ATS systems and resonate with hiring managers.
When to Use This Skill
- Reviewing or improving a software engineer's resume
- Crafting impactful achievement bullets from work experience
- Optimizing resume content for ATS keyword matching
- Tailoring a resume for a specific job description
- Understanding modern resume structure and formatting
Core Principles
The Resume's Purpose
A resume is a marketing document, not a job history. Its purpose is to:
- Pass ATS screening (keyword matching)
- Capture a recruiter's attention (6-second scan)
- Demonstrate value through quantified achievements
- Secure an interview opportunity
What Makes Engineering Resumes Different
Software engineering resumes should emphasize:
- Technical impact: Specific technologies, scale, and performance improvements
- Business outcomes: Revenue, cost savings, user growth, time savings
- Leadership signals: Mentoring, cross-team collaboration, technical decisions
- Quantification: Numbers that demonstrate scope and impact
Resume Structure Quick Reference
Recommended Section Order
- Contact Information - Name, email, phone, LinkedIn, GitHub (optional)
- Professional Summary (optional) - 2-3 sentences for senior roles
- Skills - Technical skills organized by category
- Experience - Reverse chronological, 3-5 most relevant roles
- Projects (optional) - For junior engineers or career changers
- Education - Degrees, certifications, relevant coursework
Length Guidelines
| Experience Level | Recommended Length |
|---|---|
| 0-5 years | 1 page |
| 5-10 years | 1-2 pages |
| 10+ years | 2 pages max |
Formatting Essentials
- Font: Clean, readable (Calibri, Arial, Garamond - 10-12pt)
- Margins: 0.5-1 inch
- Format: PDF (preserves formatting)
- File naming:
FirstName_LastName_Resume.pdf
What ships with it
3 files 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.
- 1mo ago First seen · 189 lines · 45 tokens per session scan A dedac64877ba
resume-optimization is a skill published in the GitHub repository zszz3/AgentRecall (594 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 1,796 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.