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 Natsummerance/readMD --skill executive-resume-writergit clone --depth 1 https://github.com/Natsummerance/readMDWrote 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/natsummerance/readmd/executive-resume-writer)<a href="https://agentmods.dev/skills/natsummerance/readmd/executive-resume-writer"><img src="https://agentmods.dev/badge/skills/natsummerance/readmd/executive-resume-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.1 | $0.00017 | $0.01997 |
| Opus 5 | $0.00009 | $0.00999 |
| Sonnet 5 | $0.00003 | $0.00399 |
| Haiku 4.5 | $0.00002 | $0.00200 |
Grade A, and why
executive-resume-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 8d 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.
This is a copy
100% identical to executive-resume-writer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Executive Resume Writer
When to Use This Skill
Use this skill when the user:
- Is applying for C-suite, VP, or Director roles
- Has 15+ years of experience in senior leadership
- Needs to emphasize strategic leadership over tactical skills
- Mentions: "executive resume", "C-suite", "VP resume", "senior leadership", "board", "executive search"
Core Capabilities
- Write resumes for C-suite and VP-level positions
- Emphasize strategic leadership and business transformation
- Showcase P&L responsibility and organizational impact
- Balance achievements with leadership philosophy
- Format for executive recruiters and board presentations
- Include board experience and industry recognition
Executive Resume Philosophy
Key Differences from Standard Resumes:
| Standard Resume | Executive Resume |
|---|---|
| Lists skills | Demonstrates leadership brand |
| Shows tasks | Shows strategic impact |
| Focuses on "what" | Focuses on "so what" |
| 1-2 pages | 2-3 pages acceptable |
| Keywords for ATS | Story for decision-makers |
| Individual contributions | Organizational transformation |
Executive Resume Structure
Recommended Sections
1. Executive Profile/Summary
2. Core Competencies (Leadership Themes)
3. Career Highlights / Key Achievements
4. Professional Experience
5. Board & Advisory Roles
6. Education & Executive Development
7. Industry Recognition (optional)
Length Guidelines
- VP/SVP: 2 pages
- C-Suite: 2-3 pages
- Board CV: Can be longer
Executive Profile Section
This replaces the standard professional summary. Should communicate your leadership brand.
Format
[TITLE/FUNCTION] EXECUTIVE
[Leadership brand statement - who you are as a leader]
[2-3 sentences on your track record with scope/scale]
[What you're known for / unique value proposition]
Example
CHIEF OPERATING OFFICER | P&L LEADERSHIP | OPERATIONAL TRANSFORMATION
Growth-focused operations executive with 20+ years scaling B2B technology companies from $50M to $500M+ in revenue. Known for building high-performance teams, operational excellence, and creating scalable infrastructure that enables rapid growth.
Track record includes 3 successful exits, 2 IPO preparations, and leading organizations of 500+ employees across 6 countries. Expertise in operational strategy, M&A integration, and digital transformation in SaaS and enterprise software environments.
Core philosophy: Build repeatable processes that scale while maintaining the agility that drives innovation.
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.
- 8d ago First seen · 307 lines · 17 tokens per session scan A 74fc63ac5b83
executive-resume-writer is a skill published in the GitHub repository Natsummerance/readMD (22 stars, last pushed 4d ago), licensed MIT. It adds 17 tokens to every session and 1,997 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to executive-resume-writer, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
gonavi-cli
Operate databases through the GoNavi headless CLI — the gonavi executable shipped in verified GitHub Release archives. Covers listing/adding/importing saved connections, running SQL queries against saved connections or ad-hoc connection files, exporting result sets to csv/json/md/html/xlsx, batch-executing SQL files…
bibverify
Verify, repair, explain, and generate BibTeX references with Bibverify's DOI-first CLI and MCP tools.
electron-expert
Expert in Electron framework, desktop app development, IPC, and cross-platform packaging. Use when the user mentions desktop, Node.js, cross platform, Windows, macOS, or Linux, or when the task involves Electron Architecture, Process Types, IPC Communication, or App Lifecycle.
memory
Use this skill when Pioneer should proactively use durable memory or recalled context: decide whether memory can improve a turn, answer from remembered user/project facts, request memory tools, search/list/get stored memories, save durable preferences or project decisions, forget memories, audit or clean up memory, or…
trellis-brainstorm
Guides collaborative requirements discovery before implementation. Creates task directory, seeds PRD, asks high-value questions one at a time, researches technical choices, and converges on MVP scope. Use when requirements are unclear, there are multiple valid approaches, or the user describes a new feature or complex…
trellis-update-spec
Captures executable contracts and coding conventions into .trellis/spec/ documents. Use when learning something valuable from debugging, implementing, or discussion that should be preserved for future sessions.