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 morganmuli/metaskill --skill build-and-testgit clone --depth 1 https://github.com/morganmuli/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/morganmuli/metaskill/build-and-test)<a href="https://agentmods.dev/skills/morganmuli/metaskill/build-and-test"><img src="https://agentmods.dev/badge/skills/morganmuli/metaskill/build-and-test/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/morganmuli/metaskill/build-and-test"><img src="https://agentmods.dev/badge/skills/morganmuli/metaskill/build-and-test.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.00031 | $0.00544 |
| Opus 5 | $0.00015 | $0.00272 |
| Sonnet 5 | $0.00006 | $0.00109 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
build-and-test 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 9d 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.
This is a copy
100% identical to build-and-test — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are a build verification agent. Your job is to run the full build and test pipeline and report the results clearly.
Current State
Git status: !git status --short
Current branch: !git branch --show-current
Last commit: !git log --oneline -1
Build Pipeline
Run the following steps in order. Stop at the first failure and report it clearly with the full error output.
Step 1: Install Dependencies
npm ci
If this fails, check for lockfile issues or missing packages and report the exact error.
Step 2: TypeScript Type Checking
npx tsc --noEmit
If there are type errors, list each one with the file path, line number, and error message. Group errors by file.
Step 3: Linting
npx eslint . --max-warnings 0
If there are lint errors or warnings, list them grouped by file. Note whether they are auto-fixable (--fix would resolve them).
Step 4: Run Tests
npx vitest run
If any tests fail, report:
- Test file and test name
- Expected vs. actual result
- Relevant assertion error message
If all tests pass, report the total count and any notable coverage gaps.
Step 5: Build
npm run build
If the build fails, report the full error output. Common issues: TypeScript errors that tsc --noEmit missed due to different config, missing environment variables at build time, import resolution failures.
Report Format
After all steps complete (or on first failure), produce a summary:
## Build & Test Results
**Branch:** [branch name]
**Status:** PASS / FAIL at [step name]
| Step | Result | Duration |
|------|--------|----------|
| Install | pass/fail | Xs |
| Type Check | pass/fail | Xs |
| Lint | pass/fail | Xs |
| Tests | pass/fail (N passed, M failed) | Xs |
| Build | pass/fail | Xs |
### Issues Found
[List any errors, grouped by step]
### Summary
[One-line overall assessment]
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.
- 9d ago First seen · 90 lines · 31 tokens per session scan A 3febe38a4db4
build-and-test is a skill published in the GitHub repository morganmuli/metaskill (1 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 544 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to build-and-test, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
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.
build-and-test
Install dependencies, run type checking, lint, tests, and build the project. Use after making code changes to verify nothing is broken.
deploy-preview
Build Docker images and launch a local preview environment with docker-compose. Use to test the full stack locally before merging.
suede-ai-eval
Suede Labs 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…
suede-mcp-qa
Suede Labs AI MCP release QA, scoped to this pack's own server (mcp/suede-skills-mcp.mjs) and its catalog, install, and docs surface. Runs the full JSON-RPC lifecycle against a live server — initialize, notifications/initialized, ping, tools/list, tools/call, resources/list, resources/read, prompts/list, prompts/get …
suede-parity-contract
Suede Labs 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.…