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 pedroiff0/awesome-skills --skill latex-cv-maintenancegit clone --depth 1 https://github.com/pedroiff0/awesome-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/pedroiff0/awesome-skills/latex-cv-maintenance)<a href="https://agentmods.dev/skills/pedroiff0/awesome-skills/latex-cv-maintenance"><img src="https://agentmods.dev/badge/skills/pedroiff0/awesome-skills/latex-cv-maintenance/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/pedroiff0/awesome-skills/latex-cv-maintenance"><img src="https://agentmods.dev/badge/skills/pedroiff0/awesome-skills/latex-cv-maintenance.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.00077 | $0.05524 |
| Opus 5 | $0.00039 | $0.02762 |
| Sonnet 5 | $0.00015 | $0.01105 |
| Haiku 4.5 | $0.00008 | $0.00552 |
Grade A, and why
latex-cv-maintenance 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LaTeX CV Maintenance (multi-language, altacv)
Overview
Mantém um currículo em LaTeX baseado em altacv.cls quando há versões em múltiplos idiomas (ex.: portuguese.tex + english.tex) e um Lattes como fonte autoritativa de dados de projetos. Usado para revisar o CV em busca de itens faltando ou inconsistentes, espelhar edições entre idiomas e confirmar que as mudanças realmente entraram no PDF.
When to Use
- Usuário pede para "revisar o CV", "atualizar o currículo", "conferir inconsistências".
- Há um .tex por idioma e os outros são "tradução direta" de um deles (PT = fonte da verdade).
- Precisa garantir que projetos/datas/cargos batem com o Lattes.
- Criar novos idiomas (ex.: "cadê o ES e FR? crie-os traduzidamente") — o CV deste usuário
já tem 4 idiomas (PT/EN/ES/FR), cada um com wrapper
*CV.tex+page1sidebarXX.texdedicados. - Não usar para gerar o XML de importação do Lattes (ver skill
lattes-xml-projetos).
Workflow
- Localize os arquivos: o main (ex.: portugueseCV.tex) faz
\input{portuguese.tex}; há um .tex por idioma e sidebars (ex.: page1sidebar.tex / page2sidebar.tex) para a barra lateral. O build costuma ser um Makefile (make portugueseCV/make englishCV) comlatexmk -lualatex. - PT é a fonte da verdade. Edite primeiro o portuguese.tex; espelhe cada mudança em TODOS os
outros idiomas (english.tex, spanish.tex, french.tex — tradução literal, sem inventar conteúdo).
Trate como edição atômica em todas as línguas. Se o CV tiver 2 idiomas só (PT/EN), espelhe PT<->EN.
2b. Para CRIAR um novo idioma (ex.: ES/FR a partir do PT), replique a estrutura de um idioma existente:
XX.tex: copieportuguese.tex, troque\selectlanguage{brazilian}pelo idioma alvo (\selectlanguage{spanish}/\selectlanguage{french}) e traduza o corpo. Ajustehl=XXnos links (Google Scholar etc.) para o idioma.page1sidebarXX.tex: copiepage1sidebar.texe traduza (Premiações→Premios/Prix, Línguas→Idiomas/Langues...).XXCV.tex: wrapper que copiaportugueseCV.tex/englishCV.tex, mas com\usepackage[brazilian,<idioma>]{babel}(KEEPbrazilianprimeiro — o\selectlanguagedo\todayno corpo depende dele) e\input{XX.tex}.Makefile: adicioneXX_PDF := XXCV.pdf,XX_SRC := XXCV.tex, targetXXCVe$(XX_PDF)e inclua emall. Veja o padrão dos targetsspanishCV/frenchCVjá existentes. Tradução é DIRETA (não adapte conteúdo). Não invente dados.
- Cross-check com o Lattes (XML ou export): confira título, período (ano/mês), cargo (Bolsista vs Voluntário), orientador(es) e natureza (Pesquisa/Extensão) de cada projeto. O CV tende a defasar quando o projeto é renomeado ou a data muda no Lattes.
- Aplique nas duas línguas e nos sidebars se a informação aparecer lá (ex.: premiações citam o título de um projeto — o título deve bater em ambos os lados).
- Verifique (obrigatório): compile e extraia o texto para confirmar que a edição entrou no PDF.
Receita em
references/verify-recipe.md. - Mantenha também as versões em Markdown sincronizadas (preferência do usuário): o repo tem
README.md(com o CV embutido em md na seção "CV em Markdown") ecurriculo.md(CV standalone em md). Ao mudar conteúdo no LaTeX, replique a mesma alteração nesses .md — o usuário os usa como fonte legível/portátil. OREADME.mdtambém documenta o build multi-idioma (tabela de arquivos por idioma + targets do Makefile).
What ships with it
3 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 · 233 lines · 77 tokens per session scan A fbd3b9e46852
latex-cv-maintenance is a skill published in the GitHub repository pedroiff0/awesome-skills (1 stars, last pushed 5d ago), licensed MIT. It adds 77 tokens to every session and 5,524 once invoked, about $0.0004 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
dx-roaster
Brutally honest developer-experience audit for a GitHub repo. Scores 10 DX dimensions (time-to-first-success, README clarity, visual proof, install, quick-start, docs, examples, community, trust, marketing), writes a shareable roast in the requested tone (brutal/honest/kind), produces a prioritized action plan ranked…
review-workflow
A review workflow for GitHub pull requests and issues, including judging whether changes can be merged or an issue can be closed. It requires read-only review, REST API access, and testing changes in practice.
mnemosyne-maintenance
Use when: upgrading Mnemosyne, diagnosing slow/hung consolidation (mnemosynesleep), fixing missing embeddings, or troubleshooting import/version mismatches.
code-review
When the user wants a thorough code review of changes, a PR, a file, or a feature branch. Use when the user says "review this," "code review," "check my code," "what's wrong with this," "review my PR," "look over this," "critique this," "review before merge," or when submitting code for quality assessment. Performs…
specification-compliance-review
Use this skill when an implementation is described as partial, passing, or complete and the task is to determine whether it actually satisfies an explicit specification. This is not a generic code review and not a re-run of the test suite. The central question is: does every normative requirement have both a correct…
dsh-requesting-code-review
A pre-commit code review process with separate checks for general quality and for matching the requested specification. A commit is a saved set of code changes in Git.