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 github-pages-portfoliogit 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/github-pages-portfolio)<a href="https://agentmods.dev/skills/pedroiff0/awesome-skills/github-pages-portfolio"><img src="https://agentmods.dev/badge/skills/pedroiff0/awesome-skills/github-pages-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/pedroiff0/awesome-skills/github-pages-portfolio"><img src="https://agentmods.dev/badge/skills/pedroiff0/awesome-skills/github-pages-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.00115 | $0.02458 |
| Opus 5.5 | $0.00046 | $0.00983 |
| Sonnet 5.5 | $0.00023 | $0.00492 |
| Haiku 4.5 | $0.00012 | $0.00246 |
Grade A, and why
github-pages-portfolio scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Verification after deploy is slow/cache-prone — and the user will say "não chegou".** Both Pages repos now have custom domains: `pedroiff0.github.io/page` 301→`www.phrandrade.com` and `pedroiff0.github.io/webpage` 30 How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Pages Portfolio
When to use
- "crie um portfólio", "página de portfólio", "site pessoal no GitHub Pages", "landing / intro / resumé site".
- Updating an existing Pages repo (e.g. pedro's
webpage= short resumé vspage= official Quartz site). - Need to list a user's GitHub repos (public AND private) on one page.
Key distinctions (ask or infer)
- Short resumé / intro (portfolio): one eye-catching page for introduction / client acquisition. For pedro this is
pedroiff0/webpage→ https://pedroiff0.github.io/webpage/. - Official full site: deep content, often Quartz/Obsidian (pedro's
pedroiff0/page). The portfolio should link to the official site, not replace it. - If both already exist, confirm which you're editing before writing.
Cross-linking a static portfolio WITH a Quartz site (pedro's two-repo reality)
When both webpage (portfolio) and page (Quartz, published at www.phrandrade.com, but GitHub Pages still serves pedroiff0.github.io/page with a 301 → phrandrade) exist:
- Add a reciprocal callout on EACH side:
- In the Quartz
content/<lang>/index.md(all 4: pt-br/en/es/fr), add a> [!abstract]callout: "Se você veio do meu portfólio de projetos…" (translate per language). This satisfies "referencie o portfólio nas index de cada idioma". - The portfolio already links out to the official site.
- In the Quartz
- Quartz index MD conventions (Obsidian/Quartz markdown): callouts use
> [!type]; inline HTML withstyle="..."works (used for.cv-cards-grid); embedded PDFs use![[assets/curriculo/x.pdf]]wikilinks; links must be full path from content root (pt-br/research/), never./relativo. - Per-language CV + repo card (what the user wanted instead of a 4-language list): replace the "download CV in every language" list with exactly TWO cards in a
.cv-cards-grid: (1) the CV PDF for THAT page's language only (/assets/curriculo/<lang>CV.pdf— portugueseCV/englishCV/spanishCV/frenchCV) and (2) a "Repositório do CV" card linking tohttps://github.com/pedroiff0/curriculo. Drop the Lattes-PDF link and the embedded![[...CV.pdf]]viewer, and don't explain compilation. One card per idiom, repo beside it. - i18n note: es/fr Quartz indexes are intentionally stub (only "tradução em preparação" + back-link to pt-br); don't over-translate them beyond the cross-link callout + the per-language CV card.
What ships with it
4 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.
- 1mo ago First seen · 76 lines · 115 tokens per session scan A 0af95d9c76b4
github-pages-portfolio is a skill published in the GitHub repository pedroiff0/awesome-skills (1 stars, last pushed 2d ago), licensed MIT. It adds 115 tokens to every session and 2,458 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
dependency-update-bot
Scans your project for outdated npm, pip, Cargo, Go, or Ruby packages. Runs a CVE security audit. Fetches changelogs, summarizes breaking changes with Gemini, and opens one PR per risk group (patch, minor, major). Includes Diagnosis Mode for install conflicts. Use when asked to update dependencies, check for outdated…
coding-worktree-recovery
Use this skill when coding-agent work is interrupted, an agent exits without a clean commit, multiple controllers target the same checkout, or the checkout produces inconsistent file/Git behavior.
github-pre-push-gates
Before pushing a branch to a shared remote, run through these gates. They prevent pushing credentials, PII, private history, or a broken tree. The skill covers the pre-PR quality phase — use github-pr-workflow for the PR lifecycle itself.
github-workflows
Use this skill for the full GitHub operating loop: 1) authenticate, 2) manage repos and remotes, 3) open and review PRs, 4) work on issues, and 5) monitor CI.
mnemosyne-maintenance
Use when: upgrading Mnemosyne, diagnosing slow/hung consolidation (mnemosynesleep), fixing missing embeddings, or troubleshooting import/version mismatches.
make-release
A release workflow for the Holix GitHub repository. It prepares a pull request, checks that automated tests pass, merges it, and creates the next numbered release.