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/qanpx skills add holger1411/astrodeck --skill qagit clone --depth 1 https://github.com/holger1411/astrodeckWhat 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.00030 | $0.00897 |
| Opus 5 | $0.00015 | $0.00449 |
| Sonnet 5 | $0.00006 | $0.00179 |
| Haiku 4.5 | $0.00003 | $0.00090 |
Grade A, and why
qa 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 3d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Skill
Canonical Sources
This skill references the following globals — read them BEFORE starting work:
system/globals/responsiveness.md— Breakpoints, test order, anti-patterns
Domain
Testing, Validation, Code Quality, Launch Readiness
KPIs
| Metric | Target | Measurement |
|---|---|---|
| Lighthouse Best Practices | >90 | Lighthouse JSON → categories.best-practices.score * 100 |
| ESLint Errors | 0 | npm run lint -- --format json |
| ESLint Warnings | 0 | npm run lint -- --format json |
| Formatting Issues | 0 | npm run format:check |
| HTML Validation Errors | 0 | npx html-validate dist/ |
Rules
Build Pipeline
# Full QA pipeline
npm run check:kpis # All static convention checks (single source of truth)
npm run lint # ESLint errors/warnings
npm run format:check # Prettier formatting
npx tsc --noEmit # TypeScript errors
npm run build # Astro build (0 errors, 0 warnings)
Pre-Launch Checklist
Content
- No placeholder content ("Lorem ipsum", "TODO", "FIXME")
- All links work (no
#orjavascript:void(0)) - Images have descriptive alt text
- Text is proofread
Branding
- Logo replaced (no longer AstroDeck default)
- Favicon set (
public/favicon.svg) - OG image created (
public/og-image.png, 1200x630px) - Site title and description in
astro.config.mjs
Legal
- Imprint present (required in DACH region)
- Privacy policy present
- Cookie banner configured (if tracking active)
Analytics & Forms
- Analytics code integrated (if desired)
- Forms submit to correct endpoints
- Forms have honeypot/CAPTCHA
Performance
- Lighthouse Performance >90
- Images optimized (WebP/AVIF, responsive sizes)
- No unnecessary
client:loaddirectives - External scripts with SRI
Lighthouse Targets
| Category | Minimum | Ideal |
|---|---|---|
| Performance | 90 | 95+ |
| Accessibility | 90 | 95+ |
| Best Practices | 90 | 95+ |
| SEO | 90 | 95+ |
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.
- 3d ago First seen · 107 lines · 30 tokens per session scan A 4cb1aa28563d
qa is a skill published in the GitHub repository holger1411/astrodeck (72 stars, last pushed 26d ago), licensed MIT. It adds 30 tokens to every session and 897 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…