Borrowing it
Nothing to install: this file belongs to benedya/octoquery. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/benedya/octoquery/main/AGENTS.mdgit clone --depth 1 https://github.com/benedya/octoqueryWrote 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/benedya/octoquery/agents-md)<a href="https://agentmods.dev/instructions/benedya/octoquery/agents-md"><img src="https://agentmods.dev/badge/instructions/benedya/octoquery/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.1 | $0.00671 | $0.00671 |
| Opus 5 | $0.00336 | $0.00336 |
| Sonnet 5 | $0.00134 | $0.00134 |
| Haiku 4.5 | $0.00067 | $0.00067 |
Grade A, and why
octoquery 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 6d 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 — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OctoQuery — agent guide
OctoQuery is a NestJS service exposing an MCP (Model Context Protocol) server over Streamable HTTP at /mcp. Each PostgreSQL database configured in mcp-sql-tools.json is exposed as one MCP tool that accepts a single query string and returns rows as JSON.
Layout
src/mcp/— MCP controller, server service, SQL tool handler, lazy database connectionssrc/auth/— OAuth 2.0 resource-server guard and RFC 9728 metadata endpointmcp-sql-tools.example.json— template for the (gitignored)mcp-sql-tools.jsontool configurationdemo/— Docker Compose playground: seeded demo databases — e-commerce (PostgreSQL), blog (MySQL), library (MariaDB), and helpdesk (SQL Server)
Commands
make run— start the service in watch mode (make helplists all targets)make test— integration tests (Jest + Testcontainers; requires Docker)make lint/make lint-fix— Biome + TypeScript checksmake demo-up/make demo-down— start/stop the demo databasesmake demo-psql— psql shell into the demo e-commerce database (PostgreSQL)make demo-mysql— mysql shell into the demo blog database (MySQL)make demo-mariadb— mariadb shell into the demo library database (MariaDB)make demo-mssql— sqlcmd shell into the demo helpdesk database (SQL Server)make mcp-inspector— MCP Inspector for manual testing
Available skills
Skills live in .agents/skills/:
- ecommerce-demo-db (
.agents/skills/ecommerce-demo-db/SKILL.md) — how to query the demo e-commerce database (users, products, orders, order_items) through thesql_ecommerce_demoMCP tool, including its schema and conventions. Use it for any question about the demo shop's users, products, orders, or revenue. - blog-demo-db (
.agents/skills/blog-demo-db/SKILL.md) — how to query the demo blog database (authors, posts, comments) through thesql_blog_demoMCP tool, including its schema and conventions. Use it for any question about the demo blog's authors, posts, comments, or views. - library-demo-db (
.agents/skills/library-demo-db/SKILL.md) — how to query the demo library database (books, members, loans) through thesql_library_demoMCP tool, including its schema and conventions. Use it for any question about the demo library's books, members, loans, or overdue returns. - helpdesk-demo-db (
.agents/skills/helpdesk-demo-db/SKILL.md) — how to query the demo helpdesk database (customers, agents, tickets) through thesql_helpdesk_demoMCP tool, including its T-SQL dialect notes and conventions. Use it for any question about the demo helpdesk's tickets, customers, agents, or resolution times.
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.
- 6d ago First seen · 32 lines · 671 tokens per session scan A 7d5fe874d014
octoquery AGENTS.md is an instructions file published in the GitHub repository benedya/octoquery (3 stars, last pushed 1mo ago), licensed MIT. It adds 671 tokens to every session, about $0.0034 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-31.
Other instructions, from other repositories
vibetags com-example-indexed-core-DocumentIndexEntry.instructions.md
Instructions for PIsberg/vibetags, covering copilot instructions for documentindexentry, core functionality, rules for method comparebysequence, thread-safety guarantee and architectural boundary constraints.
vibetags com-example-indexed-core-DocumentModel.instructions.md
Instructions for PIsberg/vibetags, covering copilot instructions for documentmodel, locked status, immutable type and domain model boundary.
plan-forge caching.instructions.md
Caching patterns for .NET — IDistributedCache, Redis, in-memory, cache-aside, TTL strategies.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).