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 agentmods add skills/julianobarbosa/claude-code-skills/github-pagesnpx skills add julianobarbosa/claude-code-skills --skill github-pagesgit clone --depth 1 https://github.com/julianobarbosa/claude-code-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/julianobarbosa/claude-code-skills/github-pages)<a href="https://agentmods.dev/skills/julianobarbosa/claude-code-skills/github-pages"><img src="https://agentmods.dev/badge/skills/julianobarbosa/claude-code-skills/github-pages.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 | $0.00068 | $0.02245 |
| Opus 5 | $0.00034 | $0.01123 |
| Sonnet 5 | $0.00014 | $0.00449 |
| Haiku 4.5 | $0.00007 | $0.00225 |
Grade A, and why
github-pages 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 4d 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 — 329 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Pages Skill
Complete guide for deploying, configuring, and managing GitHub Pages sites.
Quick Reference
| Site Type | Repository Name | URL Pattern |
|---|---|---|
| User/Org Site | <username>.github.io |
https://<username>.github.io |
| Project Site | Any repository name | https://<username>.github.io/<repo> |
Availability:
- Public repos: GitHub Free (all plans)
- Private repos: GitHub Pro, Team, Enterprise
Workflow Routing
When executing a workflow, output this notification directly:
Running the **WorkflowName** workflow from the **GithubPages** skill...
| Workflow | Trigger | File |
|---|---|---|
| QuickStart | "setup github pages", "create pages site" | workflows/QuickStart.md |
| CustomDomain | "add custom domain", "configure domain" | workflows/CustomDomain.md |
| JekyllSetup | "setup jekyll", "add jekyll theme" | workflows/JekyllSetup.md |
| ActionsWorkflow | "custom build", "github actions for pages" | workflows/ActionsWorkflow.md |
| Troubleshoot | "pages not working", "fix github pages" | workflows/Troubleshoot.md |
| Deploy | "deploy to github pages", "publish site" | workflows/Deploy.md |
Examples
Example 1: Create a new GitHub Pages site
User: "Setup GitHub Pages for my project"
→ Invokes QuickStart workflow
→ Checks if user/org or project site
→ Configures publishing source (branch or Actions)
→ Creates initial content structure
→ Verifies deployment
Example 2: Add custom domain
User: "Add my domain example.com to GitHub Pages"
→ Invokes CustomDomain workflow
→ Determines domain type (apex vs subdomain)
→ Provides DNS configuration instructions
→ Adds CNAME file or configures via Settings
→ Enables HTTPS enforcement
Example 3: Setup Jekyll theme
User: "Add a theme to my GitHub Pages site"
→ Invokes JekyllSetup workflow
→ Lists available supported themes
→ Configures _config.yml
→ Sets up custom CSS/layouts if needed
What ships with it
13 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.
- references/ActionsWorkflows.md 12 KB
- references/BestPractices.md 8.1 KB
- references/DnsConfiguration.md 7.1 KB
- references/JekyllConfiguration.md 11 KB
- references/Troubleshooting.md 8.3 KB
- scripts/check-site-status.sh 5.6 KB runs code
- scripts/verify-dns.sh 4.5 KB runs code
- workflows/ActionsWorkflow.md 7.8 KB
- workflows/CustomDomain.md 3.9 KB
- workflows/Deploy.md 5.4 KB
- workflows/JekyllSetup.md 5.7 KB
- workflows/QuickStart.md 3.0 KB
- workflows/Troubleshoot.md 6.4 KB
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.
- 4d ago First seen · 329 lines · 68 tokens per session scan A 15bd3e00f3b4
github-pages is a skill published in the GitHub repository julianobarbosa/claude-code-skills (10 stars, last pushed 9d ago), licensed MIT. It adds 68 tokens to every session and 2,245 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
implementing-infrastructure-as-code-security-scanning
This skill covers implementing automated security scanning for Infrastructure as Code (IaC) templates using tools like Checkov, tfsec, and KICS. It addresses detecting misconfigurations in Terraform, CloudFormation, Kubernetes manifests, and Helm charts before deployment, establishing policy-based governance, and…
terraform-iac-expert
Terraform and OpenTofu infrastructure as code — module design, state management, multi-environment setups, remote backends, secrets management, CI/CD integration. NOT for Pulumi, CDK, Ansible, or Kubernetes manifests.
ops-cost-optimization
Audits SaaS/PaaS, cloud commitment, and AI/LLM costs across Vercel, Supabase, AWS, and Cloudflare. Use when analyzing bills, right-sizing plans, or buying commitments.
cc-devops-skills
SRE, DevOps, Kubernetes, CI/CD, PromQL, Terraform, Docker, and incident operations playbook for building reliable delivery and operations workflows.
render
Use when deploying or fixing an app on Render — web services, background workers, cron jobs, private services, managed Postgres and Key-Value, and especially the render.yaml Blueprint. Covers deploys that fail with no open ports detected, 502s on first deploy, free-tier cold starts, and a free Postgres about to expire…
run-aiperf-benchmark
Launches, monitors, debugs, and collects one run-scoped AIPerf Kubernetes benchmark without changing its workload semantics. Use after perf.yaml and aiperf-config.yaml have been configured for a smoke-tested Dynamo deployment.