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 instructions/clidey/whodb/agents-mdgit clone --depth 1 https://github.com/clidey/whodbWrote 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/instructions/clidey/whodb/agents-md)<a href="https://agentmods.dev/instructions/clidey/whodb/agents-md"><img src="https://agentmods.dev/badge/instructions/clidey/whodb/agents-md.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.03108 | $0.03108 |
| Opus 5 | $0.01554 | $0.01554 |
| Sonnet 5 | $0.00622 | $0.00622 |
| Haiku 4.5 | $0.00311 | $0.00311 |
Grade A, and why
whodb AGENTS.md 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WhoDB Development Guide
WhoDB is a source-first data management tool. The public GraphQL API and frontend
contract are built around SourceType, SourceContract, SourceObject,
SourceObjectRef, and SourceSessionMetadata. The current execution layer is
still powered mainly by database plugins under core/src/plugins/.
AGENTS.md is the canonical agent instruction file for this repository. Tool-
specific files such as CLAUDE.md should import or point to this file instead
of duplicating these instructions.
If the ee/ directory is present, read ee/AGENTS.md for additional context. Do not add any code, comments, or references to ee/ in the CE codebase.
Git Commits — Hard Rule
Never commit to main (or any branch) without the user explicitly saying "please commit this for me" (or unambiguously equivalent wording) in that turn. This applies regardless of task framing — "merge it into main locally" or "just write the code changes in main" means apply the file changes on that branch, not create a commit. If committing seems necessary to accomplish what was asked (e.g. to merge a branch), stop and ask first instead of assuming consent.
Terminology
- "EE agent" / "ee agent" means the in-app WhoDB EE browser AI agent feature (under
ee/), NOT the coding-agent (Claude/Codex) configuration or any MCP server. When in doubt, ask which is meant before acting.
Non-Negotiable Rules
- GraphQL-first - All new API functionality via GraphQL. Never add HTTP resolvers unless explicitly needed (e.g., file downloads)
- No SQL injection - Never use
fmt.Sprintfwith user input for SQL. Use parameterized queries or GORM builders. See.agents/docs/sql-security.md - Plugin architecture - Never use
switch dbTypeorif dbType ==in shared code. All database-specific logic goes in plugins. See.agents/docs/plugin-architecture.md - Documentation requirements - All exported Go functions/types need doc comments. All exported TypeScript functions/components need JSDoc. See
.agents/docs/documentation.md - Localization requirements - All user-facing strings must use
t()with YAML keys. No fallback strings. No hardcoded UI text. When adding or updating keys, editen_USonly unless the user explicitly asks for other languages. See.agents/docs/localization.md - Verify before completing - For non-trivial tasks, define success criteria before editing. After finishing, verify: (1) type checks pass (
pnpm run build:cefor frontend,go build ./cmd/whodbfor backend), (2) no linting errors, (3) all added code is actually used (no dead code). See.agents/docs/verification.md - Show proof - When making a claim about how something outside of our codebase works, for example a 3rd party library or function, always provide official documentation or the actual code to back that up. Check online if you have to.
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 · 238 lines · 3,108 tokens per session scan A c7c71b5dd2b3
whodb AGENTS.md is an instructions file published in the GitHub repository clidey/whodb (5,017 stars, last pushed yesterday), licensed Apache-2.0. It adds 3,108 tokens to every session, about $0.0155 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 instructions, from other repositories
datahub AGENTS.md
AGENTS.md instructions for datahub-project/datahub, covering datahub — agent development guide, code navigation (lsp), essential commands, java code and python code.
graphjin AGENTS.md
AGENTS.md instructions for dosco/graphjin, covering graphjin agent guide, architectural overview, directory structure & responsibilities, build commands and coding guidelines.
datahub CLAUDE.md
Claude Code instructions for datahub-project/datahub, a project described as: The Context Platform for your Data and AI Stack.
Chat2DB AGENTS.md
AGENTS.md instructions for OtterMind/Chat2DB, covering chat2db community agent contract, context, product invariants, repository map and structural code navigation.
leoric AGENTS.md
Instructions for cyjake/leoric, covering agent guidelines, project overview, commands, architecture and conventions.
postgrebase AGENTS.md
Instructions for zhenruyan/postgrebase, covering postgrebase — agent development guide, tech stack, project structure, build & run and build (static, no cgo).