Borrowing it
Nothing to install: this file belongs to rafaelghif/antigravity-agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rafaelghif/antigravity-agents/main/.agents/skills/verification/SKILL.mdgit clone --depth 1 https://github.com/rafaelghif/antigravity-agentsWrote 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/rafaelghif/antigravity-agents/verification)<a href="https://agentmods.dev/skills/rafaelghif/antigravity-agents/verification"><img src="https://agentmods.dev/badge/skills/rafaelghif/antigravity-agents/verification.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.1 | $0.00030 | $0.01038 |
| Opus 5 | $0.00015 | $0.00519 |
| Sonnet 5 | $0.00006 | $0.00208 |
| Haiku 4.5 | $0.00003 | $0.00104 |
Grade A, and why
verification 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 today.
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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verification, Anti-Sham Testing & Autonomous Healing Protocol
Role: Principal QA Automation Architect & LLM Reliability Lead.
Overview & Trigger Conditions
Activate this skill whenever validating code modifications, running test suites, diagnosing test failures, implementing automated test suites, or checking release readiness.
Trigger Scenarios & Keywords:
- Running tests, writing unit/integration tests, test-driven development (TDD), fixing broken tests.
- Keywords:
test,tests,testing,pytest,jest,unit,e2e,assert,coverage,spec,mock,integration,verify.
Core Standards & Invariants
-
Zero Sham Tests (Anti-Tautology):
- Banned Test Anti-Patterns: Never write tests that only assert
callable(fn),hasattr(mod, fn),is not None,toBeDefined(), orassertTrue(True). - Every test MUST exercise concrete execution logic: pass varied inputs, trigger mutations, and assert on return values, state changes, and specific exception types.
- Enforce continuously via:
python3 scripts/test_quality_guard.py --check.
- Banned Test Anti-Patterns: Never write tests that only assert
-
Never Weaken Existing Tests:
- NEVER comment out, remove, or weaken assertions in existing test suites to make CI pass.
- A failing existing test is empirical proof of a regression; fix the underlying implementation, not the test.
-
Determinism & Zero Flakiness:
- Tests must run deterministically across all environments without race conditions or intermittent failures.
- Avoid sleeping in tests (
time.sleep()); await explicit events, promises, or mock external I/O clocks.
-
Test Pyramid & Mocking Discipline:
- Emphasize fast, hermetic unit tests covering edge cases: null/empty inputs, boundary limits, and error paths.
- Strict Mock Boundaries: Mocks are strictly restricted to external I/O boundaries (HTTP requests, message queues, third-party vendor APIs). Never mock internal domain models or business logic.
-
Multi-Stage Verification Gate:
- All code changes must pass all 9 technical gates:
python3 scripts/verify.py --execute --terse - Gate failures block merges; zero regressions tolerated.
- All code changes must pass all 9 technical gates:
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.
- today Changed e54c7d0eb22f
- yesterday Changed · +47 lines · +5 tokens per session 1cc3f9754b9f
- 3d ago Changed · +3 lines abc2818e5da5
- 8d ago First seen · 33 lines · 25 tokens per session scan A 8ed1bf57f53a
verification is a skill published in the GitHub repository rafaelghif/antigravity-agents (5 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 1,038 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-31.
Other skills, from other repositories
appveyor-automation
Automate Appveyor tasks via Rube MCP (Composio). Always search tools first for current schemas.
test-engineer
Automated E2E testing with Playwright including the auto-fix loop — generate test cases from the UI, run them, fix failures and re-run until passing, then produce a human-readable report. Test until it passes, not just test and report. Drives /toh-test; use whenever tests must be written, run, or made green.
e2e-testing-expert
Expert guide for End-to-End (E2E) testing with Playwright, unit/integration testing with Vitest, and CI/CD automated testing pipeline setup / Panduan ahli pengujian End-to-End (E2E) dengan Playwright, pengujian unit/integrasi dengan Vitest, dan otomatisasi CI/CD.
adapt-framework
Adapt this boilerplate's KATA test architecture, auth, schemas, variables, fixtures, CI, MCPs, and reporting to a project already reverse-engineered by project-discovery. Use for adapt framework, wire fixtures, connect boilerplate to target stack, or wire auth. Strict gate: analysis and plan first, explicit approval…
bash-scripting
Bash scripting workflow for creating production-ready shell scripts with defensive patterns, error handling, and testing.
godmode-shipping
BDB Shipping Godmode, the final gatekeeper for production releases. Use when running pre-launch checks, feature-flag rollouts, or rollback planning under Spec-Driven Development before a release ships.