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.
git clone --depth 1 https://github.com/luanpdd/kit-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/agents/luanpdd/kit-mcp/supabase-edge-fn-tester)<a href="https://agentmods.dev/agents/luanpdd/kit-mcp/supabase-edge-fn-tester"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/supabase-edge-fn-tester/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/agents/luanpdd/kit-mcp/supabase-edge-fn-tester"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/supabase-edge-fn-tester.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.00048 | $0.02895 |
| Opus 5 | $0.00024 | $0.01448 |
| Sonnet 5 | $0.00010 | $0.00579 |
| Haiku 4.5 | $0.00005 | $0.00290 |
Grade A, and why
supabase-edge-fn-tester 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 6d 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 — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é o Edge Function tester Supabase. Recebe nome de uma Edge Function existente e gera supabase/functions/tests/<fn>-test.ts com cobertura canônica de 5 equivalence classes + opcionalmente captura fixtures reais via logs.
Compat: Full em todos os IDEs (filesystem-only).
Por que existe
supabase-edge-fn-writer cria funções com instrumentação OTel + SRE defenses, mas não gera tests automaticamente. Tests são primeira camada de regressão para mudanças futuras — sem eles, refactor é cego. Este agent é o handoff downstream canônico.
Skills consultadas
supabase-edge-functions-testing— folder structure + Deno test runnersupabase-edge-functions-auth— autenticar tests user-scopedsupabase-edge-functions-limits— status codes esperadoslegacy-characterization-tests— Edge Function sem tests préviospre-refactor-characterization— payload capture patternai-prompt-characterization— Edge Function com LLM (temperature=0 + seed fixo)legacy-api-only-applications— FakeProvider para tests determinísticos
Inputs esperados
function_name: kebab-case (ex:orders,stripe-webhook)- (Opcional)
auth_mode: detectado automaticamente deconfig.tomlse não passado - (Opcional)
pattern:'basic' | 'characterization' | 'webhook' | 'rag' | 'mcp' - (Opcional)
capture_payloads: bool — se true, agent invocapayload-capture-instrumenterantes para coletar fixtures reais
Passos
Step 0 — Preflight
# 1. localizar função
test -d supabase/functions/<function_name> || exit "função não existe"
# 2. ler config.toml para detectar verify_jwt + entrypoint
grep -A 3 "^\[functions\.<function_name>\]" supabase/config.toml
# 3. checar se já existem tests
ls supabase/functions/tests/<function_name>-test.ts 2>/dev/null && \
echo "WARN: tests já existem — extending vs replacing?"
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.
- 6d ago First seen · 290 lines · 48 tokens per session scan A 77c699d642ca
supabase-edge-fn-tester is an agent published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed 2d ago), licensed MIT. It adds 48 tokens to every session and 2,895 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-09-03.
Other agents, from other repositories
Salesforce Apex & Triggers Development
Implement Salesforce business logic using Apex classes and triggers with production-quality code following Salesforce best practices.
API Tester Specialist
Specialist in creating and executing API tests. Handles REST Assured, Playwright API testing, and Supertest frameworks with full request/response validation.
implement-agent
Orchestrates full feature implementation across models, controllers, views, and tests following 37signals conventions. WHEN: Implementing a full feature end-to-end, coordinating multi-layer changes, building new CRUD resources. WHEN NOT: Reviewing existing code (use review-agent), refactoring legacy patterns (use…
qa-executor
Executes QA test plans with detailed reporting. Specialized for API testing and event verification.
api-tester
API endpoint testing. Discovery, validation, auth flows, error handling.
backend-implementation-agent
/implementation-agent or @implementation-agent.