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 leopu00/job-hunter-team --skill profile-summariesgit clone --depth 1 https://github.com/leopu00/job-hunter-teamWrote 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/leopu00/job-hunter-team/profile-summaries)<a href="https://agentmods.dev/skills/leopu00/job-hunter-team/profile-summaries"><img src="https://agentmods.dev/badge/skills/leopu00/job-hunter-team/profile-summaries/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/leopu00/job-hunter-team/profile-summaries"><img src="https://agentmods.dev/badge/skills/leopu00/job-hunter-team/profile-summaries.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 42 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 44 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 47 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00110 | $0.01737 |
| Opus 5 | $0.00055 | $0.00869 |
| Sonnet 5 | $0.00022 | $0.00347 |
| Haiku 4.5 | $0.00011 | $0.00174 |
Grade A, and why
profile-summaries 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 12d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
profile-summaries — the candidate's voice on disk
The structured YAML is great for filters and matches but says nothing about who the candidate is. The 4 MD files in summaries/ carry the narrative the Writers need to produce CVs that read like a person, not a checkbox list.
The 4 files (filenames are FIXED)
| File | UI title shown to the user | What it contains | Length cap |
|---|---|---|---|
about.md |
Chi sei | Persona summary: ruolo attuale/target, anni, settore, tratto distintivo | ~400 char |
preferences.md |
Preferenze raccontate | Modalità di lavoro, trasferimento, retribuzione, orari, ambiente | ~400 char |
goals.md |
Obiettivi e dream job | Cosa cerca nei prossimi 1-3 anni, contesto/azienda dei sogni | ~500 char |
strengths.md |
Punti di forza | 2-4 qualità concrete con esempio breve per ciascuna | ~500 char |
Path: $JHT_HOME/profile/summaries/<file>.md. Crea la dir se manca:
mkdir -p "$JHT_HOME/profile/summaries"
Filenames diversi (es. about-mario.md, goals_v2.md) sono silenziosamente ignorati dal frontend.
Style constraints (binding)
- Markdown semplice: paragrafi separati da riga vuota,
**grassetto**per sottolineare, liste solo se aiutano la leggibilità. - Nessuna tabella, nessun header
#— questi MD vivono in card UI già titolate. - Lunghezza: rispetta il cap. Niente muri di testo.
- Prima persona dell'utente:
"sono uno sviluppatore…","preferisco lavorare da remoto…". Mai terza persona ("Mario è…"). - Tono: naturale, come se l'utente parlasse di sé a un amico esperto del settore.
- Mai path / nomi file / jargon nel testo — l'utente legge "il riassunto", non "about.md".
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 99 lines · 110 tokens per session scan A e2bba9b59b36
profile-summaries is a skill published in the GitHub repository leopu00/job-hunter-team (49 stars, last pushed yesterday), licensed MIT. It adds 110 tokens to every session and 1,737 once invoked, about $0.0006 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 skills, from other repositories
persona-event-coordinator
Plan and manage events — scheduling, invitations, and logistics.
persona-researcher
Organize research — manage references, notes, and collaboration.
persona-team-lead
Lead a team — run standups, coordinate tasks, and communicate.
recipe-review-meet-participants
Review who attended a Google Meet conference and for how long.
recipe-save-email-attachments
Find Gmail messages with attachments and save them to a Google Drive folder.
recipe-draft-email-from-doc
Read content from a Google Doc and use it as the body of a Gmail message.