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 resume-quantifiergit 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/resume-quantifier)<a href="https://agentmods.dev/skills/natsummerance/readmd/resume-quantifier"><img src="https://agentmods.dev/badge/skills/natsummerance/readmd/resume-quantifier.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.02013 |
| Opus 5 | $0.00009 | $0.01007 |
| Sonnet 5 | $0.00003 | $0.00403 |
| Haiku 4.5 | $0.00002 | $0.00201 |
Grade A, and why
resume-quantifier 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 4d 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 resume-quantifier — 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 — 351 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resume Quantifier
When to Use This Skill
Use this skill when the user:
- Needs to add metrics and numbers to their resume
- Has bullets without quantifiable results
- Doesn't know what numbers to include
- Says they "don't have metrics" or "can't measure impact"
- Mentions: "add metrics", "quantify", "add numbers", "measure impact", "no data"
Core Capabilities
- Find hidden metrics in any experience
- Estimate numbers when exact data unavailable
- Create before/after comparisons
- Identify measurable impact points
- Transform vague statements into quantified achievements
- Guide users to discover their metrics
Why Quantification Matters
The Problem:
- "Managed projects" vs "Managed 12 projects worth $2M"
- "Improved processes" vs "Reduced cycle time by 40%"
- "Helped customers" vs "Resolved 50+ tickets daily with 98% satisfaction"
Studies Show:
- Resumes with numbers get 30% more attention
- Quantified bullets are 40% more memorable
- Numbers provide credibility and scale
The Quantification Framework
Categories of Metrics
1. Money
- Revenue generated
- Costs reduced/saved
- Budget managed
- Deal sizes closed
- Profit margins improved
2. Time
- Hours saved
- Cycle time reduced
- Project duration
- Response times
- Time to market
3. Percentages
- Growth rates
- Improvement percentages
- Efficiency gains
- Error reduction
- Conversion rates
4. Volume/Scale
- Number of customers/users
- Projects managed
- Team size
- Transactions processed
- Items produced
5. Quality
- Satisfaction scores
- Error rates
- Accuracy rates
- Compliance rates
- SLA adherence
6. Frequency
- Per day/week/month
- Annual totals
- Meeting cadences
- Report cycles
Finding Hidden Metrics
The Discovery Questions
For any experience, ask:
Scale Questions:
- How many people/projects/customers?
- What was the budget/revenue involved?
- How large was the team?
- How many locations/regions?
Impact Questions:
- What changed because of your work?
- What would have happened without you?
- What problems did you solve?
- What got better/faster/cheaper?
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.
- 4d ago First seen · 351 lines · 17 tokens per session scan A 6cdf56f990ff
resume-quantifier 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 2,013 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 resume-quantifier, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
trellis-finish-work
Wrap up the current session: verify quality gate passed, remind user to commit, archive completed tasks, and record session progress to the developer journal. Use when done coding and ready to end the session.
herdr
Control herdr from inside it. Manage workspaces and tabs, split panes, spawn agents, read output, and wait for state changes — all via CLI commands that talk to the running herdr instance over a local unix socket. Use when running inside herdr (HERDRENV=1).
vault-setup
Set up a machine to work with a workhub vault - check/install required software (git, Node.js, Claude Code, OpenCode), initialize the vault if needed, wire up Claude plugins, and run the OpenCode sync scripts. Use when onboarding a new machine, after a fresh vault-init, or when the harness feels half-configured.
tasks
Use this skill when Pioneer should create, inspect, update, reschedule, pause, resume, troubleshoot, or configure delivery for durable tasks, scheduled tasks, recurring tasks, interval tasks, cron jobs, background work, or existing task state.
handoff-go
Write a handoff document and launch the next agent in a split multiplexer pane (herdr or zellij), with new-window and paste-ready fallbacks when no multiplexer is in use.
post-to-slack
Post a message to a Slack channel, resolving channel/user names to IDs and adding an optional @mention or thread reply. Use when the user wants to post, share, or notify something in Slack, or when another skill needs to deliver its output to a Slack channel.