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/laurigates/claude-plugins/configure-github-pagesnpx skills add laurigates/claude-plugins --skill configure-github-pagesgit clone --depth 1 https://github.com/laurigates/claude-pluginsWrote 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/laurigates/claude-plugins/configure-github-pages)<a href="https://agentmods.dev/skills/laurigates/claude-plugins/configure-github-pages"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/configure-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.1 | $0.00033 | $0.01855 |
| Opus 5 | $0.00016 | $0.00928 |
| Sonnet 5 | $0.00007 | $0.00371 |
| Haiku 4.5 | $0.00003 | $0.00186 |
Grade A, and why
configure-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 2d 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/configure:github-pages
Check and configure GitHub Pages deployment.
When to Use This Skill
| Use this skill when... | Use another approach when... |
|---|---|
| Setting up GitHub Pages deployment for a documentation site | Configuring documentation standards or generators (/configure:docs instead) |
| Creating or updating a GitHub Actions workflow for Pages deployment | Debugging a failed GitHub Actions workflow (/configure:workflows instead) |
Migrating from peaceiris/actions-gh-pages to official actions/deploy-pages |
Editing documentation content or markdown files |
| Auditing Pages workflow for outdated action versions or missing permissions | Setting up a custom domain via DNS (manual repository settings) |
| Adding Pages deployment to a project with an existing doc generator | Configuring CI/CD workflows unrelated to documentation |
Context
- GitHub workflows: !
find . -path '*/.github/workflows/*' -maxdepth 3 \( -name '*doc*.yml' -o -name '*pages*.yml' \) - Documentation config: !
find . -maxdepth 1 \( -name 'mkdocs.yml' -o -name 'typedoc.json' -o -name 'docusaurus.config.*' \) - Docs directory: !
find . -maxdepth 1 -type d \( -name 'docs' -o -name 'site' \) - CNAME file: !
find . -maxdepth 1 -name 'CNAME' - Project standards: !
find . -maxdepth 1 -name '.project-standards.yaml'
Parameters
Parse from command arguments:
--check-only: Report compliance status without modifications (CI/CD mode)--fix: Apply fixes automatically without prompting--source <docs|site|custom>: Override source directory detection
Execution
Execute this GitHub Pages deployment configuration check:
Step 1: Detect documentation state
Identify existing documentation configuration:
| Config File | Generator | Output Directory |
|---|---|---|
typedoc.json |
TypeDoc | docs/ or configured |
mkdocs.yml |
MkDocs | site/ |
docs/conf.py |
Sphinx | docs/_build/html/ |
docusaurus.config.js |
Docusaurus | build/ |
Cargo.toml (with rustdoc) |
rustdoc | target/doc/ |
| None | Static | docs/ |
What ships with it
1 file 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.
- 2d ago First seen · 208 lines · 33 tokens per session scan A 108f379c3a34
configure-github-pages is a skill published in the GitHub repository laurigates/claude-plugins (58 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 1,855 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
healthcheck
Host security hardening and risk-tolerance configuration for OpenClaw deployments. Use when a user asks for security audits, firewall/SSH/update hardening, risk posture, exposure review, OpenClaw cron scheduling for periodic checks, or version status checks on a machine running OpenClaw (laptop, workstation, Pi, VPS).
cli-usage
Complete reference for the systemprompt CLI - 8 domains, 64+ subcommands for managing AI infrastructure, services, agents, cloud deployments, and analytics.
aspire-dev
Orchestrates Aspire distributed applications using the Aspire CLI and MCP tools. USE FOR: aspire start/stop, aspire describe, aspire doctor, view logs/traces, add integrations, debug resources, AppHost management. Also trigger for DistributedApplication.CreateBuilder, AddProject, AddContainer, or Aspire resource…
cloud-architecture
Master cloud architecture with AWS, Azure, GCP, cloud-native patterns, migration strategies, and cost optimization.
scalability-patterns
Master scalability patterns with load balancing, caching, database scaling, microservices, and horizontal scaling strategies.
kubernetes-orchestration
Master Kubernetes with pods, deployments, services, ingress, ConfigMaps, secrets, and production cluster management.