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 LuuOW/meridian-mcp --skill astro-expertgit clone --depth 1 https://github.com/LuuOW/meridian-mcpWrote 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/luuow/meridian-mcp/astro-expert)<a href="https://agentmods.dev/skills/luuow/meridian-mcp/astro-expert"><img src="https://agentmods.dev/badge/skills/luuow/meridian-mcp/astro-expert/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/luuow/meridian-mcp/astro-expert"><img src="https://agentmods.dev/badge/skills/luuow/meridian-mcp/astro-expert.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.00028 | $0.01193 |
| Opus 5 | $0.00014 | $0.00596 |
| Sonnet 5 | $0.00006 | $0.00239 |
| Haiku 4.5 | $0.00003 | $0.00119 |
Grade A, and why
astro-expert 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 10d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
astro-expert
Expert knowledge for building production-ready frontends with Astro — combining static rendering, selective hydration, and React islands for interactive components.
1) Core Architecture Principles
- Islands architecture: static Astro shell + selectively hydrated React islands
- Zero JS by default — every kilobyte of hydrated JS must justify itself with UX value
client:load— hydrate immediately (forms, critical interactivity)client:idle— hydrate when browser is idle (non-critical widgets)client:visible— hydrate when in viewport (below-the-fold islands)client:only="react"— skip SSR entirely for fully client-driven components (SSE consumers, real-time UIs)
2) Project Structure
src/
├── layouts/ # Astro layout shells (zero JS)
├── pages/ # File-based routing (.astro files)
│ └── [id].astro # Dynamic segments
├── components/
│ ├── layout/ # Pure Astro layout primitives
│ ├── ui/ # Shared React primitives (Button, Card, Badge)
│ └── features/ # React islands — business-logic components
├── lib/ # Utilities, API client, hooks
│ ├── utils.ts # cn() helper, formatters
│ ├── api.ts # Backend API client
│ └── useEventStream.ts # SSE hook
├── styles/
│ ├── tokens.css # CSS custom properties (color, spacing, radius)
│ └── app.css # Tailwind entry + base overrides
└── types/ # Shared TypeScript interfaces
3) Configuration Baseline
// astro.config.mjs
import { defineConfig } from 'astro/config';
import react from '@astrojs/react';
import tailwind from '@astrojs/tailwind';
export default defineConfig({
integrations: [
react(),
tailwind({ applyBaseStyles: false }),
],
output: 'hybrid', // static by default, opt-in SSR per page
});
Mark dynamic pages: export const prerender = false;
4) React Island Pattern
---
// pages/projects/[id].astro — static shell
import BaseLayout from '@/layouts/BaseLayout.astro';
import PipelineStream from '@/components/features/PipelineStream';
const { id } = Astro.params;
---
<BaseLayout title="Project">
<!-- client:only skips SSR — needed for SSE hooks -->
<PipelineStream projectId={id} client:only="react" />
</BaseLayout>
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.
- 10d ago First seen · 140 lines · 28 tokens per session scan A f8474e57d93d
astro-expert is a skill published in the GitHub repository LuuOW/meridian-mcp (0 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 1,193 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
astro
Build content-focused websites with Astro — zero JS by default, islands architecture, multi-framework components, and Markdown/MDX support.
astro
Build content-focused websites with Astro — zero JS by default, islands architecture, multi-framework components, and Markdown/MDX support.
astro
Build content-focused websites with Astro — zero JS by default, islands architecture, multi-framework components, and Markdown/MDX support.
astro
Build content-focused websites with Astro — zero JS by default, islands architecture, multi-framework components, and Markdown/MDX support.
astro
Build content-focused websites with Astro — zero JS by default, islands architecture, multi-framework components, and Markdown/MDX support.
astro
Build content-focused websites with Astro — zero JS by default, islands architecture, multi-framework components, and Markdown/MDX support.