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 antoinedc/MantaUI --skill verify-build-mantagit clone --depth 1 https://github.com/antoinedc/MantaUIWrote 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/antoinedc/mantaui/verify-build-manta)<a href="https://agentmods.dev/skills/antoinedc/mantaui/verify-build-manta"><img src="https://agentmods.dev/badge/skills/antoinedc/mantaui/verify-build-manta/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/antoinedc/mantaui/verify-build-manta"><img src="https://agentmods.dev/badge/skills/antoinedc/mantaui/verify-build-manta.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00021 | $0.00509 |
| Opus 5 | $0.00010 | $0.00254 |
| Sonnet 5 | $0.00004 | $0.00102 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
verify-build-manta 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 11d 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.
What it actually says
Verify Build — MANTA
What
Runs the full verification suite for the MANTA (Better UI) project.
Commands
# Typecheck (renderer + main + server)
npm run typecheck
# Tests (renderer: vitest, server: node:test)
npm test
# Server tests only (faster)
npm run test:server
When to Run
- Before marking any task done — this skill is mandatory for completion.
- After any change to:
src/renderer/(ChatPanel, chatUtils, Terminal, etc.)src/main/(opencode, pty, setup, providers, etc.)src/server/(all .mjs modules)mobile/(Capacitor config, native shells)src/shared/(types, voiceClassifier)
What Counts as Done
A task is not done until:
npm run typecheckpasses with no errors.npm testpasses all tests (renderer + server).- For mobile changes:
cd mobile && npm run apkbuilds successfully. - For mobile changes:
npm run build:mobilesucceeds. Do NOT commitmobile/www/— it is a gitignored build artifact that CI publishes on merge tomain.
Known Issues
- Renderer tests: pure utility functions only (no DOM, no Electron).
chatUtils.test.tsis the main suite. - Server tests: pure logic only (no live tmux/opencode). All server tests are in
src/server/*.test.mjs. - Mobile tests: none yet — build verification only.
Failure Modes
- Typecheck fails: fix the type error before anything else. Don't suppress with
@ts-ignore. - Tests fail: investigate the failure, fix the root cause, don't delete tests.
- Mobile build fails: check
mobile/logs, verify Capacitor config, ensure native deps are installed.
Notes
- Run
npm run test:watchfor iterative development (vitest only). - Run
npm run test:serverfor faster feedback on server changes. - The full
npm testis the gate — don't skip it.
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.
- 11d ago First seen · 60 lines · 21 tokens per session scan A 198592cea26f
verify-build-manta is a skill published in the GitHub repository antoinedc/MantaUI (12 stars, last pushed 5d ago), licensed MIT. It adds 21 tokens to every session and 509 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
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…
ralph
Self-referential loop until task completion with configurable verification reviewer.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.
webapp-testing
Start/reuse a local app, wait for readiness, inspect rendered state/console/network, act from observed selectors, and verify with evidence.
verify-bb
Verify BB user journeys in an isolated source dev app using dev-browser@next and the matching source CLI. Use after BB feature changes or when asked to verify or smoke-test BB. The feature map covers core UI and agent interfaces, every repository plugin, desktop, mobile, and hosted services; select the affected…