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 instructions/wtotded/agentic-resume-builder/claude-mdgit clone --depth 1 https://github.com/WtotdeD/agentic-resume-builderWrote 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/instructions/wtotded/agentic-resume-builder/claude-md)<a href="https://agentmods.dev/instructions/wtotded/agentic-resume-builder/claude-md"><img src="https://agentmods.dev/badge/instructions/wtotded/agentic-resume-builder/claude-md.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.00695 | $0.00695 |
| Opus 5 | $0.00347 | $0.00347 |
| Sonnet 5 | $0.00139 | $0.00139 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
agentic-resume-builder CLAUDE.md 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agentic-resume-builder Development Guidelines
What this repo is
A resume builder. Career content lives as markdown in content/; each file in
resumes/ is a YAML "lens" that selects and arranges that content for one
audience. The app renders a lens to HTML and exports it as an A4 PDF.
The profile in content/ is fictional demo data. Replace it with your own.
Active Technologies
- TypeScript 5+ (strict mode:
noUncheckedIndexedAccess,noUnusedLocals,noUnusedParameters) + Next.js 14+ (App Router), React 18+, Zod 4+, Puppeteer, Tailwind CSS 3.4+, clsx, tailwind-merge
Package Manager
Use pnpm for all operations. Do NOT use npm or yarn.
Validation
Run pnpm validate (lint + format:check + test + build) before every commit.
Authoring content
Use the content-interview skill (.claude/skills/content-interview/) to add a
job, showcase or project. It interviews the user and writes a correctly formatted
file into content/.
The two couplings, and how each one fails
expand:references an entryid— fails loudly. A config lists experience ids to render in full. An id matching no file incontent/experience/throwsexperience.expand references non-existent ID, which the render route catches and displays as an error box on the page. You will notice this one.sections:matches##headings by exact string — fails silently. A config lists the section headings it wants. A heading present in an entry but absent from the config does not render; a heading listed in the config but present in no expanded entry produces nothing. Case, spacing and&must match exactly, and there is no error, no warning, and no log line either way.
The silent one is what to watch. After changing content or configs, a clean
pnpm validate does not mean the resume renders what you intended — open
/render/<config-name> and confirm the sections you expect are actually there.
Fixed section-heading vocabulary
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 · 66 lines · 695 tokens per session scan A ad842610a9e6
agentic-resume-builder CLAUDE.md is an instructions file published in the GitHub repository WtotdeD/agentic-resume-builder (2 stars, last pushed 10d ago), licensed MIT. It adds 695 tokens to every session, about $0.0035 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 instructions, from other repositories
go-docs-mcp CLAUDE.md
Instructions for drolosoft/go-docs-mcp, covering go-docs-mcp, build & run, architecture, key decisions and tools.
vkr-builder AGENTS.md
AGENTS.md instructions for maxbarsukov/vkr-builder, covering vkr-builder, как себя вести and основные команды.
docsift CLAUDE.md
Instructions for anishmoncivarghese/docsift, covering docsift, key documents (read before making product decisions), commands, architecture (src layout, package docsift) and hard rules.
mcp-server-anydoc AGENTS.md
AGENTS.md instructions for ofershap/mcp-server-anydoc, covering mcp-server-anydoc, when to use, install (agent instructions), tools and limits.
md-anything copilot-instructions.md
Instructions for ojspace/md-anything, covering copilot instructions for md-anything, build, test, and lint commands, full suite, contributor-safe required subset and regenerate generated pdf/epub fixtures when needed.
resume-parser AGENTS.md
Instructions for dhanushk-offl/resume-parser, covering agents.md — agent configuration for resume parser skill, skill name, description, install and capabilities.