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 kouroshez/coding-os --skill astrogit clone --depth 1 https://github.com/kouroshez/coding-osWrote 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/kouroshez/coding-os/astro)<a href="https://agentmods.dev/skills/kouroshez/coding-os/astro"><img src="https://agentmods.dev/badge/skills/kouroshez/coding-os/astro.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.00110 | $0.00859 |
| Opus 5 | $0.00055 | $0.00430 |
| Sonnet 5 | $0.00022 | $0.00172 |
| Haiku 4.5 | $0.00011 | $0.00086 |
Grade A, and why
astro 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 4d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
REQUIRED BACKGROUND: You MUST also follow the core frontend-fundamentals skill (generic UI patterns) and clean-code. This skill adds Astro-specific patterns on top.
astro
Layer contract (matches structure.tree)
| Layer | May import | Never |
|---|---|---|
pages/*.astro |
layouts, components, getCollection() data |
request-time globals (runs at build) |
components/*.astro |
child components, props | page-level data fetching for the whole page |
islands (client:*) |
the leaf framework component only | wrapping a whole page/layout |
pages/api/*.ts |
lib/problem.ts, domain logic |
building an error body inline |
content/config.ts |
astro:content, Zod |
runtime side effects |
lib/problem.ts |
nothing app-specific | leaking internals to the client |
Pages and .astro frontmatter run at build time (SSG) — no request
context there. Anything needing a request lives in an endpoint or an island,
so a page stays a static, zero-JS artifact.
Rendering & islands
output: "static"is the default; a page ships zero client JS. Switch a single route tohybrid/serveronly when it genuinely needs request-time rendering — never flip the whole app.- Hydrate the narrowest island:
client:visible/client:idleoverclient:load;client:onlyonly when SSR truly cannot run. - Islands are leaf components — extract the interactive part into a framework component (React/Svelte/Vue) and keep the page/layout shell static.
Content collections
- Every content type has a Zod schema in
src/content/config.ts— that schema is the content contract, validated at build time. - Read via
getCollection()/getEntry(); consume the typeddata. Never read a frontmatter key the schema does not declare — extend the schema first. - Collections are the content SSOT: content lives in
src/content/, not inlined in pages.
Endpoints
- A file under
pages/api/exportingGET/POST/… is a server endpoint. - Success returns a thin JSON
Response; every error goes through the singlelib/problem.tsshaper (RFC 9457,docs/api-contracts/error-format.md). Unknown errors → generic message to the client, full detail to the server log.
What ships with it
1 file 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.
- 4d ago First seen · 72 lines · 110 tokens per session scan A 88822fbd20de
astro is a skill published in the GitHub repository kouroshez/coding-os (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 110 tokens to every session and 859 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
graph-mutation-plan
Cookbook for composing an applygraphmutations plan — stable entitykey patterns, the canonical label/edge vocabulary, evidence/invalidation/confidence discipline, and a worked example. Load this when building a non-trivial mutation plan.
potpie-cli
Use when the task is centered on running, explaining, configuring, or troubleshooting the potpie command: doctor, login, pot management, source registration, search, graph workbench reads/writes, and pot scope behavior.
potpie-infra-architecture
Use for project infra and architecture context: environments, adapters, runtime configuration, deployments, service dependencies, datastores, API contracts, ownership, incidents, and dependency blast radius.
screenshot-studio
Regenerate the Pisper product screenshots under docs/shots/ against the current UI. Starts an isolated dev instance, seeds fictional demo data through the real runtime APIs, captures every referenced page at the exact 2558x1380 asset size, and replaces the files. Use only when the user asks to refresh product…
css-debug
Use this skill to diagnose CSS and frontend layout issues such as positioning, overflow clipping, Tailwind class conflicts, z-index stacking, and React rendering visibility problems.
ring:validating-ux-completeness
Validating that UX specifications are complete before technical design: a read-only checklist over wireframes, states, responsive behavior, accessibility, and component-library alignment, emitting a DESIGN VALIDATED / NEEDS REVISION verdict to design-validation.md. Standalone utility — run after a product-designer…