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 OKHP3/skillz --skill okhp3-vite-github-pagesgit clone --depth 1 https://github.com/OKHP3/skillzWrote 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/okhp3/skillz/okhp3-vite-github-pages)<a href="https://agentmods.dev/skills/okhp3/skillz/okhp3-vite-github-pages"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/okhp3-vite-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.00095 | $0.01236 |
| Opus 5 | $0.00048 | $0.00618 |
| Sonnet 5 | $0.00019 | $0.00247 |
| Haiku 4.5 | $0.00010 | $0.00124 |
Grade A, and why
okhp3-vite-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 6d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
okhp3-vite-github-pages
OverKill Hill P³ · overkillhill.com · github.com/OKHP3
Use this focused runbook to keep the Abrahamic Reference Engine compatible with its client-only Vite build and GitHub Pages Actions deployment. Verify the repository before relying on any remembered version or workflow detail.
Scope
| In scope | Out of scope |
|---|---|
vite.config.ts, .github/workflows/deploy-pages.yml, production base paths, BrowserRouter, build artifacts, Pages permissions/artifacts, environment wiring, and deployment diagnosis |
Servers, databases, backend proxies, gh-pages branches, the legacy npm run deploy, secret creation, commits, pushes, and unrelated application changes |
Project contract
Treat these current facts as constraints, then re-read the files if the task may have changed them:
vite.config.tssetsbaseto/abrahamic-reference-engine/whencommand === 'build'and/otherwise. The dev server listens on0.0.0.0:5000.src/App.tsxusesBrowserRouterwithbasename={import.meta.env.BASE_URL.replace(/\/$/, '')}..github/workflows/deploy-pages.ymlruns on pushes tomainor manual dispatch, uses Pages permissions and concurrency, installs withnpm ci, builds withnpm run build, copiesdist/index.htmltodist/404.html, uploadsdist, and deploys with the Pages actions.- No environment variables are passed to the Vite build at this time.
Workflow
1. Plan
Read AGENTS.md, vite.config.ts, .github/workflows/deploy-pages.yml, package.json, src/App.tsx, and the relevant recent diff. Check git status --short. Classify the request as configuration, workflow, artifact, or diagnosis before editing. Do not change deployment settings merely because a validation command succeeds.
2. Validate the source of truth
Confirm the intended repository name, Pages base, router, build script, artifact path, trigger branch, environment variables, permissions, and fallback behavior from the files. If the requested result conflicts with the client-only boundary or the checked-in workflow, stop and report the conflict.
What ships with it
2 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.
- 6d ago First seen · 83 lines · 95 tokens per session scan A 9ea0a607137e
okhp3-vite-github-pages is a skill published in the GitHub repository OKHP3/skillz (3 stars, last pushed yesterday), licensed MIT. It adds 95 tokens to every session and 1,236 once invoked, about $0.0005 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
vastai-sdk
Vast.ai Python SDK — high-level API for GPU instances, volumes, serverless endpoints, and billing.
runbook-generator
Generates comprehensive operational runbooks for any system or process. Reads codebase, infrastructure config, and deployment scripts to produce structured runbook.md files formatted for on-call engineers. Use when you need operations documentation, incident response guides, deployment procedures, or disaster recovery…
go-tooling-security
Use when setting up Go modules/workspaces, configuring golangci-lint v2, running govulncheck, or building a Go CI quality gate. Not for app logic or non-Go audits.
kelly-devops
Product-fleet ops desk (Busabase App-in-Skill) for uptime/service health, SSL certificate expiry, domain renewal, API key rotation, cloud spend anomalies, and a review queue of agent-proposed action cards. Use when the user invokes $kelly-devops or /kelly-devops, or asks about uptime, service health checks, SSL…
neo-azure-pipelines
Use this skill when the user asks to create, review, debug, or modernize Azure Pipelines YAML for CI/CD, especially .NET builds, Azure App Service deploys, or IIS/on-premises deploys. Prefer bundled templates and verify task syntax against Microsoft docs when version-specific accuracy matters.
insforge-cli
Use this skill whenever someone needs a backend, or a task touches InsForge backend or cloud infrastructure through the InsForge CLI: projects, SQL, migrations, RLS policies, functions, storage, backups, deployments, compute, secrets, config, schedules, logs, diagnostics, advisor scans and suppressions, import/export…