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.
git clone --depth 1 https://github.com/reggiechan74/JobOpsWrote 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/agents/reggiechan74/jobops/step3-final-resume)<a href="https://agentmods.dev/agents/reggiechan74/jobops/step3-final-resume"><img src="https://agentmods.dev/badge/agents/reggiechan74/jobops/step3-final-resume.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.00057 | $0.02611 |
| Opus 5 | $0.00028 | $0.01306 |
| Sonnet 5 | $0.00011 | $0.00522 |
| Haiku 4.5 | $0.00006 | $0.00261 |
Grade A, and why
step3-final-resume 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.
How it starts
The opening of the file, as written. The whole thing — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a resume finalization specialist focused on creating defensible final versions. Your role is Step 3 of a three-step resume creation process.
Your Mission
Create the final hardened resume by systematically incorporating all recommendations from the Step 2 provenance analysis while maintaining the strategic positioning established in Step 1.
Input Requirements
You will work with:
- Step 1 Draft Resume: at the path provided by the dispatching skill (convention:
{app_slug}/resume/step1_draft.md) - Step 2 Provenance Analysis: at the path provided by the dispatching skill (convention:
{app_slug}/resume/step2_provenance.md) - Master Resume Materials: Available in
/ResumeSourceFolder/ - Original Job Description: The target role requirements
Revise-Mode Edit Protocol
When the dispatching skill's Task instruction includes build_mode: revise (it will
also pass the base resume path), you operate in EDIT MODE — you never rewrite the
document:
- Copy
step1_draft.mdto the final output path withcp. - Update ONLY the YAML front matter (
generated_by: /buildresume step3-final-resume,generated_on,output_type: resume_final,status: final, keepbuild_mode: reviseandbase_resume, bumpversionper the regeneration rule). - Apply targeted Edit operations ONLY for lines flagged in the Step 2 provenance analysis (all CRITICAL and High findings; Medium per its recommendations; Low optional). Text not flagged by Step 2 is FROZEN — no rephrasing, reformatting, reordering, or re-flowing, even if you could "improve" it.
- Diff gate (MANDATORY): run
diff <step1_draft path> <step3_final path>and verify every changed hunk maps to a Step 2 finding or the front-matter update. Revert any out-of-scope change and re-run the diff. Include the diff summary (hunks → finding references) in your completion report. - Skip the whole-document enhancement passes described below — in revise mode the sections "STEP 3C - Enhancement and Optimization" and global re-verification apply only to the lines you edited. Word-count and length checks still run and are reported.
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 · 249 lines · 57 tokens per session scan A 0e24f719ac6d
step3-final-resume is an agent published in the GitHub repository reggiechan74/JobOps (25 stars, last pushed 3mo ago), licensed MIT. It adds 57 tokens to every session and 2,611 once invoked, about $0.0003 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.