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/cameroncooke/mcpli/agents-mdgit clone --depth 1 https://github.com/cameroncooke/mcpliWhat 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.00695 | $0.00695 |
| Opus 5 | $0.00347 | $0.00347 |
| Sonnet 5 | $0.00139 | $0.00139 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
mcpli 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
src/: TypeScript source. Entry issrc/mcpli.ts; daemon code insrc/daemon/(runtime, IPC, wrapper); config insrc/config.ts; utilities insrc/utils/.tests/: Vitest specs split byunit/,integration/, ande2e/. Test helpers intests/test-helper.ts.dist/: Build output (mcpli.js,daemon/wrapper.js). Do not edit manually.scripts/: Maintenance scripts (release.sh,test-regression.sh).- Sample MCP servers for local testing:
weather-server.js,test-server.js,complex-test-server.js.
Build, Test, and Development Commands
npm run build: Bundle with tsup (targets Node 22). Outputs todist/and sets execute bits.npm run dev: Convenience rebuild (same as build) for iterative work.npm run typecheck: TypeScript checks without emit.npm run lint|npm run lint:fix: Lint (ESLint) and optionally fix.npm test: Run all tests (Vitest). Variants:test:unit,test:integration,test:e2e,coverage.- Local CLI example:
./dist/mcpli.js --help -- node weather-server.js.
Coding Style & Naming Conventions
- Formatting: Prettier (2‑space indent, single quotes, semicolons, trailing commas, width 100). Check with
npm run format:check; write withnpm run format. - Linting: ESLint + TypeScript ESLint. In
src/, avoidany, prefer explicit return types, and do not import*.jsfrom TS (no-restricted-imports). - File names: use
kebab-casefor files,PascalCasefor types/classes,camelCasefor variables/functions.
Testing Guidelines
- Framework: Vitest with Node environment; coverage via V8 (
text,html,lcov). - Location/patterns:
tests/**/**/*.test.ts. Keep fast unit tests undertests/unitand heavier flows underintegration/e2e. - Isolation: use helpers in
tests/test-helper.ts(temp dirs, daemon polling) for stable daemon tests.
Commit & Pull Request Guidelines
- Use Conventional Commits (
feat:,fix:,docs:,refactor:,test:,chore:). Example:feat: add daemon status subcommand. - PRs: include a clear description, linked issues (
closes #123), test instructions, and updateCHANGELOG.mdwhen user-facing. - Pre‑merge checklist:
npm run build,npm run typecheck,npm run lint, and passing tests.
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 · 38 lines · 695 tokens per session scan A 21b54afe690d
mcpli AGENTS.md is an instructions file published in the GitHub repository cameroncooke/mcpli (105 stars, last pushed 6mo ago), licensed MIT. It adds 695 tokens to every session, about $0.0035 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
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.