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 elevanaltd/HestAI-MCP --skill supabase-test-harnessgit clone --depth 1 https://github.com/elevanaltd/HestAI-MCPWrote 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/elevanaltd/hestai-mcp/supabase-test-harness)<a href="https://agentmods.dev/skills/elevanaltd/hestai-mcp/supabase-test-harness"><img src="https://agentmods.dev/badge/skills/elevanaltd/hestai-mcp/supabase-test-harness/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/elevanaltd/hestai-mcp/supabase-test-harness"><img src="https://agentmods.dev/badge/skills/elevanaltd/hestai-mcp/supabase-test-harness.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.00104 | $0.01736 |
| Opus 5 | $0.00052 | $0.00868 |
| Sonnet 5 | $0.00021 | $0.00347 |
| Haiku 4.5 | $0.00010 | $0.00174 |
Grade A, and why
supabase-test-harness 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 7d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
===SUPABASE_TEST_HARNESS=== META: TYPE::SKILL VERSION::"1.0.0" STATUS::ACTIVE PURPOSE::"Supabase test harness patterns: local setup, Auth Admin API test users, RLS validation, migration testing, seed sequences, rate limiting, environment detection"
SUPABASE_TEST_MASTERY::[LOCAL_SETUP+AUTH_ADMIN_API+RLS_VALIDATION+MIGRATION_TESTING+SEED_SEQUENCES]→PRODUCTION_READY
§1::PRIMARY_SOURCE_MANDATORY_FIRST
SOURCE::.hestai/state/context/test-context/RULES.md PRINCIPLE::"POC-proven pattern post-it note — ALWAYS consult BEFORE infrastructure decisions"
CONTAINS::[ supabase_setup[local_env], test_users[standardized_credentials], migration_testing[supabase_db_reset], fail_fast_guards ]
§2::DETAILED_DOCUMENTATION
SUPABASE_HARNESS::.hestai/state/context/test-context/SUPABASE-TEST-HARNESS.md→[ local_setup[docker∨cli], test_user_creation[auth_admin_api], RLS_testing, seed_procedures, preview_branch_integration, env_config ]
§3::POC_REFERENCE_WHEN_NEEDED
PROVEN_INFRASTRUCTURE::"/Volumes/HestAI-Projects/eav-ops/eav-apps/scripts-web/src/test/" FILES::[ supabase-test-client.ts::"Test client with environment detection, fail-fast guards", auth-helpers.ts::"Auth utilities with rate limiting (750ms delay)" ]
OPERATIONAL_SCRIPTS::"/Volumes/HestAI-Projects/eav-ops/eav-apps/scripts-web/scripts/" FILES::[ create-test-users-via-api.mjs::"Test user creation via Auth Admin API (used by CI)" ]
§4::CRITICAL_PATTERNS_POC_PROVEN
PATTERN_1::MIGRATION_TESTING::[ USE::supabase_db_reset_local[NOT_db_push], BECAUSE::"EMERGENCY FIX 2025-10-26 — db push fails with complex trigger functions", EVIDENCE::POC_ci.yml:105 ]
PATTERN_2::TEST_USER_CREATION::[ METHOD::auth_admin_api_via_scripts/create-test-users-via-api.mjs[NOT_SQL], BECAUSE::"Ensures proper GoTrue internal state (auth.users + auth.identities)", EVIDENCE::[POC_ci.yml:144-161, POC_scripts/create-test-users-via-api.mjs] ]
PATTERN_3::RATE_LIMITING::[ DELAY::750ms_between_auth_operations, IMPLEMENTATION::auth_delay_helper, BECAUSE::"Prevents Supabase rate limit failures", EVIDENCE::POC_src/test/supabase-test-client.ts:121-131 ]
PATTERN_4::FAIL_FAST_GUARDS::[ DETECTION::CI_misconfiguration[hardcoded_urls_blocking_preview], CODE::"if(SUPABASE_PREVIEW_URL && SUPABASE_URL.includes('127.0.0.1'))→throw('CI_MISCONFIGURATION')", BECAUSE::"Prevents 50+ minute CI hangs", EVIDENCE::POC_src/test/supabase-test-client.ts:75-81 ]
PATTERN_5::ENVIRONMENT_PRIORITY::[ ORDER::"SUPABASE_PREVIEW_URL gt 127.0.0.1:54321 gt VITE_SUPABASE_URL", BECAUSE::"Automatic environment detection (CI preview > local > remote fallback)", EVIDENCE::POC_src/test/supabase-test-client.ts:37-41 ]
PATTERN_6::SEED_SEQUENCE::[ ORDER::migrations→test_users_via_auth_api→seed_data_via_sql, BECAUSE::"Order matters for FK constraints (users must exist before data references them)", EVIDENCE::POC_ci.yml:100-168 ]
§5::TEST_USERS_STANDARDIZED
ADMIN_EMAIL::[email protected] CLIENT_EMAIL::[email protected] UNAUTH_EMAIL::[email protected] PASSWORDS::"see .env — TEST_USER_ADMIN_PASSWORD, TEST_USER_CLIENT_PASSWORD, TEST_USER_UNAUTH_PASSWORD" NOTE::"Emails are stable test fixtures. Passwords come from .env — never hardcode credentials." SOURCE::POC_src/test/supabase-test-client.ts:102-115
§6::ENVIRONMENT_CONFIGURATION
VITE_SUPABASE_URL::"https://project.supabase.co" VITE_SUPABASE_PUBLISHABLE_KEY::"sb_publishable_" SUPABASE_SECRET_KEY::"sb_secret_" SUPABASE_PREVIEW_URL::"https://preview-branch.supabase.co" SUPABASE_PREVIEW_ANON_KEY::"sb_publishable_preview_*" VITEST_INTEGRATION::true
§7::GITGUARDIAN_EXCLUSIONS
PATH_EXCLUSIONS::["packages//src/test/**", "apps//src/test/", "/.test.ts", "**/.test.tsx"] PATTERN_EXCLUSIONS::["test-mock-.*", "test-project\.supabase\.co", "127\.0\.0\.1:54321", "test-password-(admin|client|unauth)-123"] RATIONALE::"Real credentials in .env (gitignored), test fixtures non-functional"
§8::AGENT_CONSULTATION
CONSULT::[ security-specialist::"Credential management, GitGuardian patterns, test data isolation", critical-engineer::"Production risk from test infrastructure failures", universal-test-engineer::"Actual test writing (delegate, don't implement)" ]
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.
- 7d ago First seen · 160 lines · 104 tokens per session scan A 974e86512112
supabase-test-harness is a skill published in the GitHub repository elevanaltd/HestAI-MCP (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 104 tokens to every session and 1,736 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
api-tester
A tool for creating and checking API tests from the real API contract and implementation. An API is the agreed way that software sends requests and receives responses.
backend/testing-guide
A guide for writing backend tests: small unit tests, tests that check connected parts such as an API and database, and end-to-end tests that follow a complete user flow.
endpoint-probe
Probes each major Agent Monitor API route — /api/stats, /api/analytics, /api/sessions, /api/pricing/cost, /api/workflows/runs, /api/cc-config/overview — and reports each one's HTTP status, latency, and response shape, flagging which are reachable. Use to verify a dashboard install is wired up correctly.
emulate-seed
Generate emulate seed configs for stateful API emulation. Wraps Vercel's emulate tool for GitHub, Vercel, Google OAuth, Slack, Apple Auth, Microsoft Entra, AWS, Okta, Clerk, Resend, Stripe, and MongoDB Atlas APIs — full state machines, not mocks. Use when setting up test environments, CI pipelines, integration tests…
api-smoke-testing
Start the dev server, discover API routes from the codebase, hit every endpoint, and report which ones return errors.
Kafka Event-Driven Testing
Test Kafka-based event-driven systems, producer and consumer integration tests with Testcontainers, schema compatibility gates, idempotency and ordering verification, dead-letter handling, and end-to-end event flow assertions.