Borrowing it
Nothing to install: this file belongs to wirnat/gibrun. 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/wirnat/gibrun/main/AGENTS.mdgit clone --depth 1 https://github.com/wirnat/gibrunWrote 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/wirnat/gibrun/agents-md)<a href="https://agentmods.dev/instructions/wirnat/gibrun/agents-md"><img src="https://agentmods.dev/badge/instructions/wirnat/gibrun/agents-md/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/instructions/wirnat/gibrun/agents-md"><img src="https://agentmods.dev/badge/instructions/wirnat/gibrun/agents-md.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.00795 | $0.00795 |
| Opus 5.5 | $0.00318 | $0.00318 |
| Sonnet 5.5 | $0.00159 | $0.00159 |
| Haiku 4.5 | $0.00080 | $0.00080 |
Grade A, and why
gibrun 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 2mo 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 — 24 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
Core MCP logic lives in src/index.ts, which registers every tool (Postgres queries, HTTP executor, Go build helpers, file IO, and DAP hooks). TypeScript output is written to build/ via tsc, and package.json points MCP clients to build/index.js. Repository-level docs (README.md, PROJECT_OVERVIEW.md, DAP_INTEGRATION.md, EXAMPLES.md, TROUBLESHOOTING_DAP.md) explain usage scenarios; reference config.example.json when wiring Claude, Cursor, or other hosts. The test-example/ folder provides an end-to-end playground: sample-api.go, schema.sql, go.mod, and a Dockerfile for spinning up the demo API alongside PostgreSQL, matching the docker-compose.yml stack.
Build, Test, and Development Commands
npm install— install the TypeScript SDK, pg client, and other runtime deps.npm run dev— runtsc --watch, continuously emittingbuild/index.jswhile you iterate on tools.npm run build— perform a one-shot strict compile/type-check; this must pass before publishing or cutting a release.npx @modelcontextprotocol/inspector node build/index.js— attach the MCP Inspector to validate tool definitions and responses after building.cd test-example && go run sample-api.go(ordocker compose up) — launch the sample API plus database so you can practice the postgres→HTTP→verification workflow end to end.
Coding Style & Naming Conventions
Write modern TypeScript targeting ES2022 with Node16 resolution, as enforced by tsconfig.json. Use 4-space indentation, explicit async return types, and keep tool handlers small, composable functions (e.g., handlePostgresQuery). Tool identifiers stay snake_case to match MCP expectations, while variables and functions remain camelCase. Prefer structured errors that return { content, isError } payloads instead of throwing. Run npm run build before pushing to ensure the compiler’s strict mode stays green; no separate formatter runs today, so follow the existing style and keep descriptive JSDoc-style comments to explain non-obvious logic.
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.
- 2mo ago First seen · 24 lines · 795 tokens per session scan A 6168a4968826
gibrun AGENTS.md is an instructions file published in the GitHub repository wirnat/gibrun (1 stars, last pushed 11mo ago), licensed MIT. It adds 795 tokens to every session, about $0.0032 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-08-31.
Other instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.