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 Nevaberry/nevaberry-plugins --skill astro-knowledge-patchgit clone --depth 1 https://github.com/Nevaberry/nevaberry-pluginsWrote 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/nevaberry/nevaberry-plugins/astro-knowledge-patch)<a href="https://agentmods.dev/skills/nevaberry/nevaberry-plugins/astro-knowledge-patch"><img src="https://agentmods.dev/badge/skills/nevaberry/nevaberry-plugins/astro-knowledge-patch/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/nevaberry/nevaberry-plugins/astro-knowledge-patch"><img src="https://agentmods.dev/badge/skills/nevaberry/nevaberry-plugins/astro-knowledge-patch.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.00008 | $0.02105 |
| Opus 5.5 | $0.00003 | $0.00842 |
| Sonnet 5.5 | $0.00002 | $0.00421 |
| Haiku 4.5 | $0.00001 | $0.00211 |
Grade A, and why
astro-knowledge-patch 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
fetch(request: Request) { How it starts
The opening of the file, as written. The whole thing — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Astro Knowledge Patch
Use this skill before creating, upgrading, or debugging an Astro project. Check the breaking changes first, then open the reference matching the task.
Index
| Reference | Topics |
|---|---|
| Upgrading and breaking changes | Runtime and dependency baselines, promoted flags, changed defaults, removed APIs |
| Routing, rendering, and caching | Server islands, redirects, endpoints, prerendering, advanced routing, response caching |
| Content, data, and Actions | Content loaders, live collections, generated schemas, Astro DB, Actions, incremental content |
| Markdown and MDX | TOML, remote images, highlighting, heading IDs, SmartyPants, unified and Sätteri |
| Images, fonts, and styles | Responsive images, Sharp, SVG components and optimization, Fonts API |
| Security, sessions, and environment | Typed environment variables, CSP, sessions, cookies |
| Adapters and integrations | Netlify, Node, Cloudflare, Vercel, React, Svelte, sitemap, Adapter API |
| Configuration, tooling, and APIs | Typed config, programmatic build, host allowlists, logging, background servers |
| Starlight | Sidebar generation, locale fallback links, CJK spacing |
Breaking changes first
Astro 7 project checks
- Markdown and MDX use Sätteri by default with GFM enabled. Select
unified()explicitly if the project depends on remark or rehype plugins. - Queued rendering is stable and automatic. Remove
experimental.queuedRendering. - Move
cache,routeRules, andloggerout ofexperimental. - Replace
--experimentalJsonwith--json. - Put a custom standard-pipeline handler at
src/fetch.ts; without that file, Astro uses the normal request pipeline.
What ships with it
10 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.
- coverage.json 2.8 KB
- references/adapters-and-integrations.md 8.0 KB
- references/configuration-tooling-and-apis.md 6.0 KB
- references/content-data-and-actions.md 7.3 KB
- references/images-fonts-and-styles.md 7.5 KB
- references/markdown-and-mdx.md 4.0 KB
- references/routing-rendering-and-caching.md 6.0 KB
- references/security-sessions-and-environment.md 5.9 KB
- references/starlight.md 875 B
- references/upgrading-and-breaking-changes.md 4.5 KB
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 · 243 lines · 8 tokens per session scan A 864bfe4b8696
astro-knowledge-patch is a skill published in the GitHub repository Nevaberry/nevaberry-plugins (23 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 2,105 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.clientCapabilities, ctx.enrich, ctx.content), and when to use each.
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
api-telemetry
Catalog of OpenTelemetry instrumentation built into framework @cyanheads/mcp-ts-core — spans, metrics, completion logs, env config, runtime caveats, custom instrumentation patterns, and cardinality rules. Use when enabling OTel export, adding custom spans or metrics in services, debugging missing telemetry, looking up…
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
polish-docs-meta
Finalize documentation and project metadata for a ship-ready MCP server. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…