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 jamestorrevillas/dev-skills --skill resume-portfoliogit clone --depth 1 https://github.com/jamestorrevillas/dev-skillsWrote 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/jamestorrevillas/dev-skills/resume-portfolio)<a href="https://agentmods.dev/skills/jamestorrevillas/dev-skills/resume-portfolio"><img src="https://agentmods.dev/badge/skills/jamestorrevillas/dev-skills/resume-portfolio/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/jamestorrevillas/dev-skills/resume-portfolio"><img src="https://agentmods.dev/badge/skills/jamestorrevillas/dev-skills/resume-portfolio.svg" alt="Reviewed on agentmods" width="80" 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.00055 | $0.00673 |
| Opus 5 | $0.00028 | $0.00336 |
| Sonnet 5 | $0.00011 | $0.00135 |
| Haiku 4.5 | $0.00006 | $0.00067 |
Grade A, and why
resume-portfolio 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 11d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resume & Portfolio
Core Principle
Your resume is not a job description of what you did — it's a curated argument for why you're the right person for a specific role. Every line should earn its place.
Resume Writing Formula
For Each Role / Project
[Action verb] [what you built/did] [using/with what]
[that resulted in / achieving] [measurable outcome]
Examples:
WEAK: "Worked on BTT module development"
STRONG: "Built Query Clarity Assessment Agent achieving 95%+ test
coverage, unblocking production deployment for the team"
WEAK: "Helped with frontend development"
STRONG: "Implemented LaunchDarkly feature flagging for BTT UI,
enabling safe gradual rollout to production users"
Strong Action Verbs by Category
- Built/Created: Developed, Engineered, Architected, Implemented
- Improved: Optimized, Reduced, Accelerated, Automated
- Led: Spearheaded, Owned, Drove, Championed
- Collaborated: Partnered, Coordinated, Mentored, Facilitated
What to Quantify
If you can answer any of these, include the number:
- How many users/requests does this serve?
- What % did you improve (performance, coverage, speed)?
- How many team members did this affect?
- How much time did it save?
- What was the scale? (lines of code, services, endpoints)
If you can't quantify, describe impact on the team or project instead.
Portfolio Project Writeup Template
## [Project Name]
**Problem:** [What problem does this solve? Why does it matter?]
**My Role:** [What specifically did YOU build or own?]
**Technical Approach:** [Key decisions and why you made them]
**Result:** [What was the outcome? What would you do differently?]
**Stack:** [Technologies used]
LinkedIn / Professional Bio
Structure
- Who you are — current role + years of experience
- What you do — specific skills and focus areas
- What you've built — 1-2 concrete accomplishments
- What you're interested in — where you want to grow
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.
- 11d ago First seen · 92 lines · 0 tokens per session scan A af256d8aa378
resume-portfolio is a skill published in the GitHub repository jamestorrevillas/dev-skills (3 stars, last pushed 5mo ago), licensed MIT. It adds 55 tokens to every session and 673 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-31.
Other skills, from other repositories
go-dependency-audit
Go dependency audit specialist for CVE scanning (govulncheck), license risk triage, outdated dependency detection, upgrade impact analysis, and supply chain security. ALWAYS use when auditing go.mod dependencies, running govulncheck, checking license compatibility, planning dependency upgrades, or investigating supply…
pg-migration
PostgreSQL schema migration safety reviewer and DDL generator. ALWAYS use when writing, reviewing, or planning PostgreSQL schema changes — ALTER TABLE, CREATE/DROP INDEX, column type changes, constraint additions, RLS policy changes, or any DDL touching production tables. Covers lock-level analysis, CREATE INDEX…
api-integration-test
Create, maintain, and run gated Go integration tests for internal APIs and service-to-service clients (HTTP/gRPC). Use for endpoint verification, contract checks with real runtime config, opt-in execution, timeout/retry safety, and integration failure triage in Go services.
fuzzing-test
A Go testing guide for generating fuzz tests, which repeatedly try varied inputs to find crashes and unexpected behavior. It first checks whether the code is suitable for fuzzing.
go-benchmark
Go performance benchmarking and pprof profiling specialist. ALWAYS use when writing benchmark functions (testing.B), generating or reading pprof profiles, interpreting flame graphs, finding memory allocation hotspots, comparing implementations with benchstat, or measuring ns/op / B/op / allocs/op. In Go code contexts…
create-pr
Create evidence-backed pull requests to the GitHub main branch with strict preflight, quality, and security gates. Use when users ask to create/submit/open/update a PR to main (including private repos), decide draft vs ready state, and provide reviewer-ready context for team review.