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/dpaul20/qacito/agents-mdgit clone --depth 1 https://github.com/dpaul20/qacitoWhat 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.00904 | $0.00904 |
| Opus 5 | $0.00452 | $0.00452 |
| Sonnet 5 | $0.00181 | $0.00181 |
| Haiku 4.5 | $0.00090 | $0.00090 |
Grade A, and why
qacito AGENTS.md scanned grade A with 1 finding 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 2d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
**Every caller-supplied path must go through `resolveSafe(root, p)` before any filesystem or process operation.** There are no exceptions. Passing a raw string from tool input to `fs`, `path.resolve`, or `child_process` How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — QAcito Code Review Rules
These rules are enforced on every commit by Gentleman Guardian Angel.
Review only .ts and .js files; ignore test files (*.test.ts, *.spec.ts).
Architecture
Vertical slice structure is mandatory. Every tool must live under src/tools/{tool-name}/ and expose exactly these files:
schema.ts— Zod input schema and inferred type. No business logic.handler.ts— Pure async function. No MCP imports. Returns plain data.index.ts— Singleregister(server: McpServer)function. The only file allowed to import from@modelcontextprotocol/sdk.
src/server/register-tools.ts is the only place that imports tool slices (index.ts files that register with MCP). If a new tool slice is imported outside register-tools.ts, flag it.
Exception — src/batch/orchestrator.ts: Batch mode drives Claude directly without the MCP server layer. It imports tool handler.ts files directly (not index.ts slices). This is intentional and is not a violation.
Handlers must not import from @modelcontextprotocol/sdk. MCP coupling belongs exclusively in index.ts.
Security
Every caller-supplied path must go through resolveSafe(root, p) before any filesystem or process operation. There are no exceptions. Passing a raw string from tool input to fs, path.resolve, or child_process without resolveSafe is a critical violation.
Never trust projectRoot from tool input directly — always pass it through resolveSafe or use it as the root argument to resolveSafe.
TypeScript
All Zod schemas use .safeParse() in index.ts before passing to the handler. Never call a handler with unvalidated input.
Schemas export both the Zod object and the inferred type:
export const MyInputSchema = z.object({ ... });
export type MyInput = z.infer<typeof MyInputSchema>;
Array index access returns T | undefined (noUncheckedIndexedAccess is enabled). Never cast arr[i] to T — guard it or use nullish coalescing.
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.
- 2d ago First seen · 90 lines · 904 tokens per session scan A 1b7a43d83e4f
qacito AGENTS.md is an instructions file published in the GitHub repository dpaul20/qacito (0 stars, last pushed 9d ago), licensed MIT. It adds 904 tokens to every session, about $0.0045 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). 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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.