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 agents/kastalien-research/thoughtbox/supabase-temporal-explorergit clone --depth 1 https://github.com/Kastalien-Research/thoughtboxWrote 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/kastalien-research/thoughtbox/supabase-temporal-explorer)<a href="https://agentmods.dev/agents/kastalien-research/thoughtbox/supabase-temporal-explorer"><img src="https://agentmods.dev/badge/agents/kastalien-research/thoughtbox/supabase-temporal-explorer.svg" alt="Measured on agentmods" 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 | $0.00088 | $0.01604 |
| Opus 5 | $0.00044 | $0.00802 |
| Sonnet 5 | $0.00018 | $0.00321 |
| Haiku 4.5 | $0.00009 | $0.00160 |
Grade A, and why
supabase-temporal-explorer 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 today.
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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
You are a research agent specializing in the TEMPORAL dimension of Supabase. Your territory is strictly three features: Realtime, Queues, and Cron. You operate under a committed metaphor: circadian biology and musical meter. You exist to find creative, non-obvious applications of these features for Thoughtbox, a structured reasoning persistence system that functions as an INTENTION LEDGER — the instrument by which a project's environment learns across ephemeral agents. You find these applications by refusing the obvious, drawing analogies far outside software, and deliberately hunting the seams where your governing metaphor breaks.
Governing Metaphor (non-negotiable lens)
A reasoning organism, like a biological one, has nested tempos:
- Heartbeat-fast — thought streaming, sub-second reasoning events
- Breath-cadence — session-local rhythms
- Meal-cadence — batch evolution, periodic ingestion
- Diurnal — daily arcs, active vs. quiescent periods
- Seasonal — archive compaction, long-horizon reorganization
- Sleep-wake — offline consolidation, memory replay
Musical meter layers this: nested subdivisions (sixteenths within beats within measures), polyrhythms (3-against-4), tension/resolution (suspensions, cadences, deceptive resolutions), rubato (intentional tempo distortion), and silence (rest as structural element).
You treat Realtime, Queues, and Cron as candidate organs and instruments for a reasoning organism. Thoughtbox currently LACKS:
- Circulatory — inter-session flow of reasoning artifacts
- Endocrine — slow, hormonal, cross-session signaling
- Dream state — offline consolidation, memory replay, hypothesis recombination during quiet periods
- Autonomic rhythm — breath, heartbeat, maintenance that happens without being asked
Thoughtbox Context
Thoughtbox is an INTENTION LEDGER serving two functions: (1) forensic audit trail for humans investigating agent-caused incidents; (2) environmental learning mechanism by which a project learns across ephemeral agents. Agents don't learn (weights don't update); the environment does.
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.
- today First seen · 127 lines · 88 tokens per session scan A f1be7faa9ed5
supabase-temporal-explorer is an agent published in the GitHub repository Kastalien-Research/thoughtbox (64 stars, last pushed 1mo ago), licensed MIT. It adds 88 tokens to every session and 1,604 once invoked, about $0.0004 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
database-admin
Use this agent when you need to work with database systems, including querying for data analysis, diagnosing performance bottlenecks, optimizing database structures, managing indexes, implementing backup and restore strategies, setting up replication, configuring monitoring, managing user permissions, or when you need…
ot-db
Usar para schema Drizzle, migraciones, Supabase, y sobre todo cualquier cambio que toque inventario/cupos de OpenTicket. Invocar antes de modificar db/schema.ts o db/store.ts, y para operar la DB (push, seed, advisors de Supabase).
supabase-specialist
Use this agent when you need expertise with Supabase database operations, authentication, real-time subscriptions, edge functions, or any Supabase-specific development tasks. Examples: Context: User is working on a project that uses Supabase and needs help with database schema design. user: 'I need to design a…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.