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 fusengine/agents --skill astro-securitygit clone --depth 1 https://github.com/fusengine/agentsWrote 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/fusengine/agents/astro-security)<a href="https://agentmods.dev/skills/fusengine/agents/astro-security"><img src="https://agentmods.dev/badge/skills/fusengine/agents/astro-security/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/fusengine/agents/astro-security"><img src="https://agentmods.dev/badge/skills/fusengine/agents/astro-security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.01098 |
| Opus 5.5 | $0.00013 | $0.00439 |
| Sonnet 5.5 | $0.00007 | $0.00220 |
| Haiku 4.5 | $0.00003 | $0.00110 |
Grade A, and why
astro-security 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 20d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Also covers the adapters' staticHeaders option (formerly experimentalStaticHeaders) for emitting CSP as HTTP headers instead of a meta tag, and the 7.1+ kind scoping to script-src-elem/-attr and style-src-elem/-attr. States the known limitations: CSP is inactive in dev mode (test with build + preview), incompatible with <ClientRouter /> view transitions, and unsupported for Shiki's inline styles. Does not cover general deployment adapter setup beyond the CSP header wiring (astro-deployment).
Astro Security
Agent Workflow (MANDATORY)
Before ANY implementation, spawn 3 agents in parallel, one Agent call each with a name:
- fuse-ai-pilot:explore-codebase - Analyze existing security config, adapters, headers
- fuse-ai-pilot:research-expert - Verify latest Astro 7 CSP docs via Context7/Exa
- mcp__context7__query-docs - Check CSP compatibility with deployment adapter
After implementation, run fuse-ai-pilot:sniper for validation.
Overview
When to Use
- Enabling CSP in an Astro project (stable in v6.0.0)
- Configuring
security.cspinastro.config.mjs - Adding SHA-256/384/512 hashes for external scripts or styles
- Using nonces for dynamic script injection
- Setting up adapter
staticHeadersfor CSP as HTTP headers
CSP in Astro
Content Security Policy is stable since Astro 6.0 (previously experimental) and unchanged in Astro 7. When enabled:
- Astro automatically generates SHA hashes for all bundled scripts and styles
- Injects a
<meta http-equiv="content-security-policy">in each page's<head> - Supports
script-srcandstyle-srcdirectives by default - Since 7.1: hashes/resources accept
{ hash | resource, kind: 'element' | 'attribute' | 'default' }to target*-src-elem/*-src-attr
What ships with it
8 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.
- 20d ago Changed · +1 lines 998db77115cc
- 1mo ago Changed cddb9c583c61
- 1mo ago First seen · 94 lines · 33 tokens per session scan A 630f5802bb33
astro-security is a skill published in the GitHub repository fusengine/agents (32 stars, last pushed 5d ago), licensed MIT. It adds 33 tokens to every session and 1,098 once invoked, about $0.0001 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
radin-record
Log bugs, follow-ups, ideas or feedback raised this session as backlog entries that outlive the conversation. Use for /radin-record or any ask to save something for later, even a vague one ("add the findings"): scan the whole session.
radin-do
Record one ad-hoc prompt as a backlog entry, then execute just that task. Use for /radin-do .
radin-stats
Show the stats/gain output of every companion tool that ships one, side by side.
radin-batch
Work backlog tasks via sub-agents, prioritized, one commit each; plans first the entries radin-record flagged as needing a plan. Use for "work through my backlog", or name an epic or task to run only those.
designing-interfaces
Creates a design system for software with a UI. Use when a project has a user interface and architecture is confirmed — whether creating from scratch or extracting patterns from existing code.
orchestrating-software-dev
Runs software development projects from idea to completion. Use when starting a software project, adding a feature, fixing a bug, or resuming an in-progress build.