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/haongo232/nestjs-devtools-mcp/agents-mdgit clone --depth 1 https://github.com/HaoNgo232/nestjs-devtools-mcpWrote 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/haongo232/nestjs-devtools-mcp/agents-md)<a href="https://agentmods.dev/instructions/haongo232/nestjs-devtools-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/haongo232/nestjs-devtools-mcp/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 | $0.00682 | $0.00682 |
| Opus 5 | $0.00341 | $0.00341 |
| Sonnet 5 | $0.00136 | $0.00136 |
| Haiku 4.5 | $0.00068 | $0.00068 |
Grade A, and why
nestjs-devtools-mcp 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 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.
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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
This is a pnpm monorepo with two published packages and local apps:
packages/plugin:@nestjs-devtools-mcp/plugin, a NestJS module that runs inside the user app and exposes/_dev/mcp.packages/server:nestjs-devtools-mcp, a lightweight MCP STDIO bridge that discovers and proxies to local plugin endpoints.demo-app: local NestJS demo for manual integration checks.test-nestjs-app: minimal fixture app for development.docs: installation and development documentation.
Source files live in each package’s src. Unit tests live beside source under src/__tests__ or collector-specific __tests__ directories.
Build, Test, and Development Commands
Use pnpm from the repository root:
pnpm install: install workspace dependencies.pnpm run build: build all workspace packages with TypeScript.pnpm run test: run Jest tests in each package.pnpm run lint: lint all TypeScript files usingeslint.config.mjs.pnpm run format: format TypeScript files with Prettier.pnpm run ci: run format, lint, build, and tests.pnpm --filter @nestjs-devtools-mcp/plugin publish --access public: publish the NestJS plugin package.pnpm --filter nestjs-devtools-mcp publish --access public: publish the MCP bridge package.
Package-scoped examples: pnpm --filter @nestjs-devtools-mcp/plugin test and pnpm --filter nestjs-devtools-mcp build.
Coding Style & Naming Conventions
Write TypeScript and follow existing NestJS naming in packages/plugin: services end in .service.ts, controllers in .controller.ts, guards in .guard.ts, and specs in .spec.ts. Keep bridge files in packages/server framework-free.
ESLint forbids unused variables unless prefixed with _, forbids explicit any outside tests, and forbids non-null assertions. Prettier is the formatting source of truth.
Testing Guidelines
Tests use Jest with ts-jest and match *.spec.ts. Keep tests close to the behavior being changed. Add or update tests for new tools, contracts, discovery behavior, guards, collectors, and logger changes. Run pnpm run test before opening a PR; use package-scoped test commands while iterating.
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 · 49 lines · 682 tokens per session scan A 715512279f4a
nestjs-devtools-mcp AGENTS.md is an instructions file published in the GitHub repository HaoNgo232/nestjs-devtools-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 682 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
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.