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 agentmods add skills/holger1411/astrodeck/readmenpx skills add holger1411/astrodeck --skill readmegit clone --depth 1 https://github.com/holger1411/astrodeckWrote 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/holger1411/astrodeck/readme)<a href="https://agentmods.dev/skills/holger1411/astrodeck/readme"><img src="https://agentmods.dev/badge/skills/holger1411/astrodeck/readme.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 | $0.00031 | $0.00642 |
| Opus 5 | $0.00015 | $0.00321 |
| Sonnet 5 | $0.00006 | $0.00128 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
readme 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AstroDeck README Skill
This skill provides access to the complete AstroDeck project documentation.
When to Use This Skill
- Starting work on an AstroDeck project
- Creating new pages or components
- Understanding available sections and layouts
- Troubleshooting installation or configuration
- Learning about the project structure
- Finding deployment instructions
Instructions
- Read the README.md file at the project root for comprehensive documentation
- The README contains:
- Project overview and features
- Installation instructions
- Development commands
- Complete project structure
- Usage guide for pages, components, and layouts
- Component library overview (15+ sections)
- Customization guide
- Deployment instructions
- Troubleshooting guide
- AI-friendly development information
Quick Reference
Key Commands
npm install # Install dependencies
npm run dev # Start development server (localhost:4321)
npm run build # Build for production
npm run preview # Preview production build
Three-Tier Architecture
AstroDeck uses a three-tier hierarchy of building blocks:
| Tier | What | Count | Location |
|---|---|---|---|
| Components | Small UI primitives (Button, Dialog, Tabs...) | 11 | src/components/ui/ |
| Sections | Full page sections (Hero, Pricing, FAQ...) | 16 | src/components/sections/ |
| Pages | Complete page templates (SaaS, Portfolio...) | 11 | src/pages/ |
Components are the smallest pieces. Sections combine components into full-width blocks. Pages assemble sections into complete websites.
Project Structure
src/
├── components/sections/ # TIER 2: Hero, CTA, Features, Pricing, FAQ, etc.
├── components/ui/ # TIER 1: shadcn/ui components (Button, Card, Dialog...)
├── layouts/ # BaseLayout, FullWidthLayout, AuthLayout, ArticleLayout
├── pages/ # TIER 3: Complete pages with file-based routing
├── content/ # Content Collections (blog)
├── styles/globals.css # Design tokens
└── lib/utils.ts # Utility functions
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 · 85 lines · 31 tokens per session scan A dcd628868ca9
readme is a skill published in the GitHub repository holger1411/astrodeck (73 stars, last pushed 28d ago), licensed MIT. It adds 31 tokens to every session and 642 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…