Database Metrics Digest Agent with Claude Code
You may not edit a query, add a filter, widen a date range, or run SQL of your own. That instruction is the entire product here, and the harness's job is to be the sort of agent that does not improvise around it. Claude Code follows an explicit constraint through a run instead of optimising past it, which is what you want holding a database connection.
Watch it work before it's live
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
08:30 daily metrics tick
It is 08:30 in Melbourne and all six queries return in under two seconds for the meal kit database. Signups came back at 148 against 131 yesterday, active subscriptions are flat at 9,204, and the failed payment count is the same three as the day before.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect PostgreSQL
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Metrics queries
The exact read only SELECT statements you want run each morning, each with the name it should carry in the digest. This list is the only SQL the agent will ever run.
Digest style
How the digest should read, which movements are worth flagging (for example signups down more than 20 percent), and who to tag when a query fails.
Runs on Claude Code
Preselected for this page — connect your Claude Code account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Why Claude Code for this agent
Runs the list, nothing else
Six statements in the order given, no additions and no rewrites. Discipline matters more than capability on this one.
Refuses a non-select
An entry in your list that is not a plain SELECT has to be reported as not a select rather than executed. A careful harness treats that as a rule, not a suggestion.
Before you fork
Is instruction-following enough protection for production?
No, and the template says as much: connect a read-only role or a replica and the guarantee moves from the prompt into the database. The harness choice lowers the chance of an improvised query, while the role makes it impossible. Do both, in that order of trust.
Run it with a different agent
Put Database Metrics Digest Agent to work on Claude Code
Free to start. Guided setup, a test run against staged conversations, and it's live.