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 SpillwaveSolutions/publishing-astro-websites-agentic-skill --skill publishing-astro-websitesgit clone --depth 1 https://github.com/SpillwaveSolutions/publishing-astro-websites-agentic-skillWrote 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/spillwavesolutions/publishing-astro-websites-agentic-skill/publishing-astro-websites)<a href="https://agentmods.dev/skills/spillwavesolutions/publishing-astro-websites-agentic-skill/publishing-astro-websites"><img src="https://agentmods.dev/badge/skills/spillwavesolutions/publishing-astro-websites-agentic-skill/publishing-astro-websites/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/spillwavesolutions/publishing-astro-websites-agentic-skill/publishing-astro-websites"><img src="https://agentmods.dev/badge/skills/spillwavesolutions/publishing-astro-websites-agentic-skill/publishing-astro-websites.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.00111 | $0.07553 |
| Opus 5.5 | $0.00044 | $0.03021 |
| Sonnet 5.5 | $0.00022 | $0.01511 |
| Haiku 4.5 | $0.00011 | $0.00755 |
Grade A, and why
publishing-astro-websites 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 1mo 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 1mo ago First seen · 1,233 lines · 111 tokens per session scan A 6807623f5236
publishing-astro-websites is a skill published in the GitHub repository SpillwaveSolutions/publishing-astro-websites-agentic-skill (31 stars, last pushed 9mo ago), with no licence file. It adds 111 tokens to every session and 7,553 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
jamstack-storefront
Build a blazing-fast storefront with Next.js or Astro that pre-renders product pages as static HTML and fetches live data from commerce APIs.
api-catalog
Reference for all Nixopus API operations callable via nixopusapi(method, path, body).
domain-tls-routing
Diagnose domain resolution, TLS certificate provisioning, and reverse proxy routing issues. Use when a domain is not resolving, TLS certificates fail, proxy returns 502/503/504, or custom domains are stuck in pending status.
failure-diagnosis
Diagnose deployment failures, container crashes, and networking issues using structured pattern matching on logs and container state. Use when a deployment fails, a container crashes or exits unexpectedly, or the app is unreachable after deployment.
deploy-flow
Full deploy pipeline — source detection, hints-driven analysis, project creation, deployment monitoring, and live URL delivery. Load when the user wants to deploy an application.
node-deploy
Build and deploy Node.js applications — version detection, package managers, framework-specific builds, monorepo support, and Dockerfile patterns. Use when deploying a Node.js, JavaScript, or TypeScript project, or when package.json is detected in the repository.