Borrowing it
Nothing to install: this file belongs to sidduHERE/agentpool. 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/sidduHERE/agentpool/main/AGENTS.mdgit clone --depth 1 https://github.com/sidduHERE/agentpoolWrote 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/sidduhere/agentpool/agents-md)<a href="https://agentmods.dev/instructions/sidduhere/agentpool/agents-md"><img src="https://agentmods.dev/badge/instructions/sidduhere/agentpool/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/sidduhere/agentpool/agents-md"><img src="https://agentmods.dev/badge/instructions/sidduhere/agentpool/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.00340 | $0.00340 |
| Opus 5.5 | $0.00136 | $0.00136 |
| Sonnet 5.5 | $0.00068 | $0.00068 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
agentpool 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.
What it actually says
Talk to the user as a fellow senior developer.
AgentPool helps users get the most out of the coding-agent subscriptions they pay for: surface each provider's live usage limits and offload work to whichever still has headroom when the active provider nears its 5-hour or weekly cap. It is a control plane, not an auto-router. Keep provider/model judgment with the primary agent.
Project guardrails:
- Treat the committed docs as the public source of truth, especially
README.md,docs/architecture.md,docs/onboarding.md,docs/mcp-tools.md, anddocs/usage-detection.md. - Use Python 3.11+.
- Use tmux as the first runtime.
- Preserve explicit provider selection. Do not add
provider=auto. - Do not implement browser scraping, credential storage, model ranking, silent overage, silent merge, or silent push behavior.
- Add fake-provider coverage before relying on real provider adapters.
- Prefer worktree isolation for mutating tasks.
- Use subprocess argument arrays; avoid shell strings for untrusted input.
- Store sessions, events, usage snapshots, artifacts, and file leases in SQLite.
- Keep artifacts outside the repo by default under
~/.agentpool/artifacts.
When AgentPool tools are available:
- Call inventory or usage before delegating.
- Choose provider/model/harness explicitly.
- Prefer
read_onlyisolation for exploration and review. - Use
worktreeisolation for edits. - Spawn narrow tasks.
- Observe, steer, interrupt, collect, and terminate deliberately.
- Do not merge or push worker changes without user approval.
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 · 29 lines · 340 tokens per session scan A 7218dc8ee279
agentpool AGENTS.md is an instructions file published in the GitHub repository sidduHERE/agentpool (0 stars, last pushed 2mo ago), licensed MIT. It adds 340 tokens to every session, about $0.0014 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.