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 xvirobotics/metaskill --skill deploy-previewgit clone --depth 1 https://github.com/xvirobotics/metaskillWrote 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/xvirobotics/metaskill/deploy-preview)<a href="https://agentmods.dev/skills/xvirobotics/metaskill/deploy-preview"><img src="https://agentmods.dev/badge/skills/xvirobotics/metaskill/deploy-preview/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/xvirobotics/metaskill/deploy-preview"><img src="https://agentmods.dev/badge/skills/xvirobotics/metaskill/deploy-preview.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.00026 | $0.00585 |
| Opus 5.5 | $0.00010 | $0.00234 |
| Sonnet 5.5 | $0.00005 | $0.00117 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
deploy-preview 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.
curl -sf http://localhost:3000/api/health || echo "HEALTH CHECK FAILED" Copies of this mod
1 near-identical copy found in the catalogue:
- deploy-preview — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a deployment preview agent. Your job is to build and launch a local preview environment using Docker, then verify it is healthy.
Current State
Current branch: !git branch --show-current
Git status: !git status --short
Deployment Steps
Step 1: Verify Docker is Available
docker --version && docker compose version
If Docker is not available, report that Docker must be installed and stop.
Step 2: Stop Any Existing Preview
docker compose -f docker-compose.yml down --remove-orphans 2>/dev/null || true
Step 3: Build Docker Images
Build the application image using the multi-stage Dockerfile:
docker compose -f docker-compose.yml build --no-cache
If the build fails, report the full error output. Common issues: missing files in build context (check .dockerignore), npm install failures, TypeScript compilation errors.
Step 4: Start Services
docker compose -f docker-compose.yml up -d
Wait for services to be healthy:
echo "Waiting for services to start..."
sleep 5
docker compose -f docker-compose.yml ps
Step 5: Run Database Migrations
docker compose -f docker-compose.yml exec -T app npx prisma migrate deploy
If migrations fail, report the error. Common issues: database not ready yet (may need longer wait), migration conflicts.
Step 6: Health Check
Verify the application is responding:
curl -sf http://localhost:3000/api/health || echo "HEALTH CHECK FAILED"
If the health check fails, inspect the logs:
docker compose -f docker-compose.yml logs --tail=50 app
Step 7: Report
## Preview Deployment Results
**Branch:** [branch name]
**Status:** RUNNING / FAILED at [step]
### Services
| Service | Status | Port |
|---------|--------|------|
| app | running/stopped | 3000 |
| db | running/stopped | 5432 |
| client | running/stopped | 5173 |
### Access URLs
- API: http://localhost:3000/api
- Frontend: http://localhost:5173
- Health: http://localhost:3000/api/health
### Cleanup
To stop the preview environment:
docker compose -f docker-compose.yml down
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 · 103 lines · 26 tokens per session scan A ec6f97c6063a
deploy-preview is a skill published in the GitHub repository xvirobotics/metaskill (73 stars, last pushed 8mo ago), licensed MIT. It adds 26 tokens to every session and 585 once invoked, about $0.0001 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
suede-ai-eval
Suede AI eval design and coverage audit: AI-SPEC, failure-mode rubric with severity scoring, concrete pass/fail eval cases, coverage and infrastructure scores, and mechanical acceptance gates. Use when a change ships LLM, RAG, agent, classifier, prompt, or generated-media behavior, or when asked to write evals for an…
suede-parity-contract
Suede AI cross-surface canon discipline: hold one canonical answer across every surface that states it (web, iOS, Android, docs, a second service) by generating a contract from the reference surface and making the others assert against it, so a divergence fails a test instead of reaching a user or an answer engine.…
api-test
Run API integration tests against the running backend, verify endpoints return expected responses and status codes. Use after deploying a preview or starting the dev server.
deploy-preview
Build Docker images and launch a local preview environment with docker-compose. Use to test the full stack locally before merging.
build-and-test
Install dependencies, run type checking, lint, tests, and build the project. Use after making code changes to verify nothing is broken.
visual-qa
Runs rigorous visual QA across web, terminal, and paginated surfaces: an Apple HIG-based checklist, paired light/dark captures at phone and desktop widths, screenshot evidence, and a per-item PASS/FAIL verdict. Use for any UI build or change, or when asked whether a page, component, or TUI looks right or follows the…