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/rvforest/nox-mcp/agents-mdgit clone --depth 1 https://github.com/rvforest/nox-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/rvforest/nox-mcp/agents-md)<a href="https://agentmods.dev/instructions/rvforest/nox-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/rvforest/nox-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.01220 | $0.01220 |
| Opus 5 | $0.00610 | $0.00610 |
| Sonnet 5 | $0.00244 | $0.00244 |
| Haiku 4.5 | $0.00122 | $0.00122 |
Grade A, and why
nox-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 4d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides essential project information and development standards for coding agents working on the nox-mcp project.
Project Overview
nox-mcp is a Python application for creating AI generated commit messages based on code changes.
- Repository: https://github.com/rvforest/nox-mcp
- Documentation: https://nox-mcp.readthedocs.io
- License: MIT
- Python Version: 3.10+
- Main Dependencies: No runtime dependencies by default. Development and documentation dependencies are defined in
pyproject.toml(dev: Ruff, pyrefly, pytest, pytest-cov, pre-commit, nox; docs: Sphinx, myst-parser, furo, sphinx-autodoc2)
Architecture Overview
The project is organized into several core components:
Directory Structure
The project follows a standard layout:
src/nox_mcp/— package sourcetests/— test suite mirroring thesrc/structuredocs/— documentation source and build filesnoxfile.py— nox sessions for running tests, docs, linting, and other tasks.github/— CI workflows.pre-commit-config.yaml— local pre-commit hooks configuration
Development Standards
Development Environment Setup
- Prerequisites: Python 3.10+, Git, uv package manager
- Setup: Run
uv syncto create virtual environment and install dependencies - Workflow: Create feature branches, make changes, test, commit, and open PRs
Code Quality Standards
Code Style and Formatting
- Tool: Ruff (Black-compatible formatting + linting)
- Commands:
- Format code:
uv run nox -s format - Check linting:
uv run nox -s lint - Check all:
uv run nox -s check
- Format code:
Type Hints
- Required: All public functions, classes, and methods must have type hints
- Tool: pyrefly for static type checking
- Command:
uv run nox -s types
Documentation
- Style: Google-style docstrings for all public APIs
- Tool: Sphinx with autodoc2, myst_parser extensions
- Commands:
- Build docs:
uv run nox -s docs - Live docs:
uv run nox -s livedocs
- Build docs:
- Include usage examples in docstrings where applicable.
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.
- 4d ago First seen · 146 lines · 1,220 tokens per session scan A bc1e820de6ba
nox-mcp AGENTS.md is an instructions file published in the GitHub repository rvforest/nox-mcp (0 stars, last pushed 9mo ago), licensed MIT. It adds 1,220 tokens to every session, about $0.0061 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.