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 agentmods add skills/gridaco/grida/ee-billingnpx skills add gridaco/grida --skill ee-billinggit clone --depth 1 https://github.com/gridaco/gridaWhat 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 | $0.00127 | $0.01410 |
| Opus 5 | $0.00063 | $0.00705 |
| Sonnet 5 | $0.00025 | $0.00282 |
| Haiku 4.5 | $0.00013 | $0.00141 |
Grade A, and why
ee-billing 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 3d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ee-billing
This is the surface skill for billing — the workflow once the
ee anchor has placed billing on the EE side and
the contributor setup is done. Setup itself is documented; cite it,
don't restate it:
- docs/contributing/billing — local Stripe + Metronome sandbox, cloudflared tunnel, env vars, troubleshooting.
- docs/wg/platform/billing/ — design notes: AI credits master plan, Metronome integration, known issues.
- docs/platform/billing — user-facing copy.
Stable surface (the contract)
These shapes are locked. A change that breaks any of them must be intentional and called out in the PR description.
grida_billing.*schema — not REST-exposed. Public reads go throughv_billing_*views; writes only throughfn_billing_*RPCs. Don't add a new direct-access surface; add a view or an RPC. Schema discipline lives indatabase/supabase/AGENTS.md.public.fn_billing_apply_stripe_event— the only place Stripe-driven subscription state mutates. Mutating from a new direction (UI form, ad-hoc RPC, hand-written migration) corrupts the projector model.public.fn_billing_apply_metronome_event— same role for Metronome credit / alert /payment_gateevents.- Webhook receivers —
/webhooks/stripeand/webhooks/metronomeare the only billing ingress; both are signature-verified perGRIDA-SEC-001. editor/lib/billing/metronome.ts— the service module surface:provisionOrg,addStripeChargedCommit,setAutoReload,getEntitlement,ingestUsageEvent. New billing actions go through this module, not adjacent to it.
Substrates
Two external clouds; both use per-contributor sandbox accounts. Credentials are never shared. Live keys are refused at boot.
- Stripe — subscriptions + payment processing. Provision via
pnpm tsx editor/scripts/billing/cli.ts setup:stripe. Idempotent; re-run after everysupabase db reset(writes price IDs into the catalog). - Metronome — AI credit ledger. Provision via
pnpm tsx editor/scripts/billing/cli.ts setup:metronome. Same idempotency / re-run rule.
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.
- 3d ago First seen · 121 lines · 127 tokens per session scan A 0e202e727f06
ee-billing is a skill published in the GitHub repository gridaco/grida (2,629 stars, last pushed 12d ago), licensed Apache-2.0. It adds 127 tokens to every session and 1,410 once invoked, about $0.0006 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-30.
Other skills, from other repositories
react-hook-form
Correct React Hook Form usage anywhere in the monorepo — data flow, subscriptions, reset, dirty state, number inputs, and controlled-input rules. Load this BEFORE writing or modifying ANY form code, adding a field to an existing form, touching watch/useWatch/formState/getValues/setValue/reset, wiring a form into a…
safe-sql-execution
Use whenever code will build, return, fetch, or execute SQL that runs against a user's real Postgres database — even when the request reads like an ordinary feature or bug fix and never says "security," "injection," or "SafeSqlFragment." This covers: writing or editing any pg-meta function, query builder, or endpoint…
studio-e2e-tests
Write and run Playwright E2E tests for Supabase Studio (e2e/studio). Use when asked to run e2e tests, write new E2E tests, or debug flaky or failing Playwright tests. Covers running commands, avoiding race conditions, waiting strategies, selectors, helper functions, and CI vs local differences.
studio-mock-api-tests
Component tests for Supabase Studio that mock API requests at the network layer with MSW. Use when writing or reviewing a component test that exercises a React Query hook or mutation, or when migrating an existing test away from vi.mock('@/data/...'). Covers the customRender + addAPIMock template and the jsdom/MSW…
ask-the-docs
Answer questions about the Supabase docs app (apps/docs) using documented architecture, build pipeline, and review-pattern notes, and apply feature-design principles (codebase reuse, coding minimalism) when proposing or critiquing changes. Use when the user asks "how does X work in the docs app?", "where does Y…
clickhouse-logs-queries
Write, review, and migrate Supabase logs queries against the ClickHouse-backed logs table (the logs.all.otel analytics endpoint). Use this whenever a task involves Logs Explorer SQL, the logattributes map, querying a log source (edgelogs, postgreslogs, authlogs, etc.), translating an old BigQuery cross join…