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 ourobx/agent-ebpf --skill neongit clone --depth 1 https://github.com/ourobx/agent-ebpfWrote 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/ourobx/agent-ebpf/neon)<a href="https://agentmods.dev/skills/ourobx/agent-ebpf/neon"><img src="https://agentmods.dev/badge/skills/ourobx/agent-ebpf/neon/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/ourobx/agent-ebpf/neon"><img src="https://agentmods.dev/badge/skills/ourobx/agent-ebpf/neon.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.00076 | $0.01905 |
| Opus 5.5 | $0.00030 | $0.00762 |
| Sonnet 5.5 | $0.00015 | $0.00381 |
| Haiku 4.5 | $0.00008 | $0.00191 |
Grade A, and why
neon 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 1mo 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Neon Postgres
The database is opt-in (AGENTS.md §0.5): use it only when the app needs data
that outlives a browser session or is shared across devices. Otherwise ship no
migrations, don't import @/lib/db, and keep state in localStorage / zustand.
This template ships a ready-made, dual-mode database integration:
- Configured (env var set, e.g. deployed): real Neon Postgres.
- Not configured (sandbox live preview): the DB falls back to a local
PGLite (embedded WASM Postgres), so the preview always renders. Build
against the
@/lib/dbhelper; both modes work with the same API.
Packages are preinstalled — do not npm install them: pg (node-postgres,
the regular Postgres driver) and @electric-sql/pglite (local DB fallback).
For user accounts, sign-in, and reading the current user, see the separate
auth skill — this skill is just the database.
Turning the database on
Set deploy.database to true in .grok/app-env.json:
{ "VITE_AUTH_ENABLED": "false", "deploy": { "database": true } }
That is what tells the platform to provision Neon for the deployed app; leave it
false and the deploy gets no DATABASE_URL, so the app silently runs on a
throwaway PGLite that loses its rows. Shipping migrations/*.sql, or sign-in,
provisions one regardless — this flag is for an app that queries @/lib/db
without either. It is not a VITE_ key and never reaches the browser.
Env vars — do not create a .env file
Never write a .env / .env.local / .env.example for the database. In
the sandbox live preview, leave DATABASE_URL unset — @/lib/db automatically
uses embedded PGLite. When the app is deployed, the platform injects
DATABASE_URL (Neon); you do not provision or write it yourself.
| Var | Where | Purpose |
|---|---|---|
DATABASE_URL |
server | Neon connection string when deployed (optional — PGLite fallback if unset) |
Never hardcode it; never expose non-VITE_ vars to the client.
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.
- 1mo ago First seen · 158 lines · 76 tokens per session scan A 87e0fe9b6479
neon is a skill published in the GitHub repository ourobx/agent-ebpf (1 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 1,905 once invoked, about $0.0003 per session on Opus 5.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-04.
Other skills, from other repositories
alloydb-basics
Manages clusters, instances, and backups for AlloyDB for PostgreSQL, and integrates with AlloyDB Model Context Protocol (MCP) tools for automated database operations. Use when creating, configuring, or administering AlloyDB databases. Do NOT use for general PostgreSQL instances (e.g. Cloud SQL) or other GCP databases.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
db-repair
Auto-fix gbrain's Postgres access so the brain stays available. When any gbrain command or MCP tool result carries a GBRAINDBACCESS marker (or an operator reports the brain database is down), run the hardcoded gbrain db-repair ladder: diagnose, apply the safe tier, verify. The action is ALWAYS the hardcoded command …
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…
volcengine-rds-postgresql
A tool for operating PostgreSQL databases hosted by Volcano Engine's managed database service. PostgreSQL is a relational database used to store structured application data.
analyzing-insights-across-teams
Analyze PostHog insights, dashboards, or teams beyond the current project by querying the prod Postgres replicas synced into the dogfood data warehouse (US project 2, "PostHog App + Website"). Use when asked to analyze insights across all teams or projects, another team's insights, or fleet-wide insight/dashboard…