StarNet is a local-first desktop harness for creating AI agents and arranging them in a pixel-art space station whose layout represents their capabilities, permissions, and workflow. It lets people run real model calls and tools through multiple bounded agents, using their own provider keys or accounts and optionally messaging the station through chat services. The catalogue entries are skills that extend or support work performed by StarNet agents.
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 androoAGI/starnet --skill publish-sitegit clone --depth 1 https://github.com/androoAGI/starnetWrote 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/androoagi/starnet/publish-site)<a href="https://agentmods.dev/skills/androoagi/starnet/publish-site"><img src="https://agentmods.dev/badge/skills/androoagi/starnet/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/androoagi/starnet/publish-site"><img src="https://agentmods.dev/badge/skills/androoagi/starnet/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.00050 | $0.02976 |
| Opus 5.5 | $0.00020 | $0.01190 |
| Sonnet 5.5 | $0.00010 | $0.00595 |
| Haiku 4.5 | $0.00005 | $0.00298 |
Grade A, and why
publish-site 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 12d 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 — 192 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 Commander built (or you built for them) and put it online on infrastructure the Commander 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, confirm the target, deploy through a provider ladder, verify the live URL with a real request, and keep rollback one step away.
This covers static sites and single-page-app build output (plain HTML/CSS/JS, or the dist/ or build/ folder from Vite, a Next.js static export, Astro and the like). It does not cover server-side runtimes; for those, deploy-checklist is the closer fit.
When to use
- 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 made.
- Update an already-published site with new content (a redeploy is a new version).
- Roll back a bad deploy to the previous version.
- Pick a host: they do not care where, they just want a URL.
Prerequisites: check before anything else
This skill relies on command-line tools that must ALREADY be installed and signed in on the Commander's machine. Check with shell.exec, in this order, and read each result:
| Provider | Installed? | Signed in? |
|---|---|---|
| (always) | git --version |
|
| GitHub Pages (default) | gh --version |
gh auth status |
| Cloudflare Pages | wrangler --version |
wrangler whoami |
| Netlify | netlify --version |
netlify status |
You need git plus at least ONE provider that is both installed and signed in.
If none is ready, stop. Tell the Commander plainly: "Publishing needs one of these tools, installed and signed in: the GitHub CLI (cli.github.com), Cloudflare's Wrangler (developers.cloudflare.com), or the Netlify CLI (docs.netlify.com). Install one from its official site, sign in with its own login command, then ask me again." Do not install a CLI yourself, do not start a sign-in flow, and never ask for a token or password in chat.
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.
- 12d ago First seen · 192 lines · 50 tokens per session scan A 9559852c00aa
publish-site is a skill published in the GitHub repository androoAGI/starnet (1,468 stars, last pushed 3d ago), licensed MIT. It adds 50 tokens to every session and 2,976 once invoked, about $0.0002 per session on Opus 5.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-10-04.
Other skills, from other repositories
land-and-deploy
Land and deploy workflow. (gstack).
publish-site
Versioned site deploys to GitHub/Cloudflare/Netlify Pages.
release-publish
Publish an approved Orchard release.
release-review
Review Orchard deployment manifests.
orchard-release
Check deployment evidence and recovery conditions.
orchard-review
Review a release proposal.