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 aivrar/portable-hermes-agent --skill publish-sitegit clone --depth 1 https://github.com/aivrar/portable-hermes-agentWrote 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/aivrar/portable-hermes-agent/publish-site)<a href="https://agentmods.dev/skills/aivrar/portable-hermes-agent/publish-site"><img src="https://agentmods.dev/badge/skills/aivrar/portable-hermes-agent/publish-site/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/aivrar/portable-hermes-agent/publish-site"><img src="https://agentmods.dev/badge/skills/aivrar/portable-hermes-agent/publish-site.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.00019 | $0.02200 |
| Opus 5 | $0.00010 | $0.01100 |
| Sonnet 5 | $0.00004 | $0.00440 |
| Haiku 4.5 | $0.00002 | $0.00220 |
Grade A, and why
publish-site 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 8d 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.
1. Build → 2. Preview for sign-off → 3. Commit + tag (version-before-deploy) → 4. Deploy via the provider ladder → 5. Verify the live URL with `curl` and report it. This is a copy
100% identical to publish-site — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publish Site
Take a website, dashboard, or web app the user built (or you built for them) and put it online on infrastructure the user owns — GitHub Pages by default, Cloudflare Pages or Netlify when they need more. The discipline: preview locally for sign-off, version every deploy with a git tag, deploy through a provider ladder, verify the live URL with a real HTTP check, and keep rollback one command away.
This skill covers static sites and SPA build output (plain HTML/CSS/JS, or the dist//build/ folder from Vite/Next-export/Astro/etc.). It does not cover server-side runtimes — for throwaway serverless deploys with zero account setup, use the cloudflare-temporary-deploy optional skill instead.
When to Use
Load this skill when the user asks to:
- Put a site online — "publish this", "host this somewhere", "give me a link I can share"
- Deploy a dashboard, report, portfolio, docs site, or prototype you just generated
- Update an already-published site with new content (redeploy = new version)
- Roll back a bad deploy to the previous version
- Pick a host — they don't care where, they just want a URL
Prerequisites
At least ONE authenticated provider CLI (check in this order):
- GitHub Pages (default):
gh auth statussucceeds. Needsgittoo. - Cloudflare Pages:
wrangler whoamisucceeds (orCLOUDFLARE_API_TOKENis set). Install:npm i -g wrangleror usenpx wrangler@latest. - Netlify (fallback):
netlify statussucceeds. Install:npm i -g netlify-cli.
Plus:
- A directory of static output to publish (site root or a
dist//build/folder). If the project needs a build step, run it first and publish the output directory, never the source. - For local preview sharing:
cloudflared(optional —python3 -m http.servercovers local-only preview).
How to Run
All commands below run via the terminal tool from the site's project directory. The pipeline is always the same five moves:
- Build → 2. Preview for sign-off → 3. Commit + tag (version-before-deploy) → 4. Deploy via the provider ladder → 5. Verify the live URL with
curland report it.
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.
- 8d ago First seen · 158 lines · 19 tokens per session scan A d6c66ce995d2
publish-site is a skill published in the GitHub repository aivrar/portable-hermes-agent (217 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 2,200 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to publish-site, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
release-nyx
Ship a new nyx-local-ai release end to end — bump versions consistently, run the quality gates (typecheck, smoke tests, package), install locally, tag and push so CI publishes the installer artifacts. Use when the user asks to release, ship, publish, bump the version, or cut a new build of the extension.
app-release
Use when the user asks to release a new version, ship a build, or publish a Skill Zoo release. Also use when a tag push results in Homebrew 404 errors or missing artifact failures.
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.
npm-release
Use when publishing or preparing to publish an npm package from this repository, especially the Skill Zoo CLI package under packages/cli. Also use when npm publish fails because of duplicate versions, npm authentication, browser authentication, dist-tag propagation, tarball contents, bin entry issues, or…
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
cpn-release-patch
Use when backporting the commits between two release tags onto a hotfix branch in cloud-pi-native/console: find the patch milestone and duplicate those commits onto the tag with jj.