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/zerotrust-labs/solodit-mcp/agents-mdgit clone --depth 1 https://github.com/zerotrust-labs/solodit-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/zerotrust-labs/solodit-mcp/agents-md)<a href="https://agentmods.dev/instructions/zerotrust-labs/solodit-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/zerotrust-labs/solodit-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.00541 | $0.00541 |
| Opus 5 | $0.00270 | $0.00270 |
| Sonnet 5 | $0.00108 | $0.00108 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
solodit-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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
src/contains the TypeScript source;src/index.tsis the MCP server entry point.dist/holds compiled JavaScript output fromtscand is generated.- Root config files include
package.json,tsconfig.json,eslint.config.js, and Prettier configs. - Documentation lives in
README.md,USAGE.md, andQUICK_START.md.
Build, Test, and Development Commands
npm run devruns the server directly from TypeScript viatsx.npm run buildcompiles TypeScript intodist/.npm run startruns the compiled server (node dist/index.js).npm run watchruns the TypeScript compiler in watch mode.npm run lintandnpm run lint:fixrun ESLint checks and fixes.npm run formatandnpm run format:checkrun Prettier formatting.npm run type-checkrunstsc --noEmitfor type validation.
Coding Style & Naming Conventions
- Formatting is handled by Prettier (2-space indentation, semicolons, double quotes, 80-char line width).
- Linting is enforced via ESLint with TypeScript support.
- Use camelCase for variables/functions, PascalCase for types/classes, and kebab-case for filenames where applicable.
- Keep changes focused in
src/and avoid editing generateddist/files.
Testing Guidelines
- There are no unit tests in this repository today; rely on
npm run type-check,npm run lint, andnpm run buildas the primary quality gates. - If you add tests in the future, place them under a
tests/or__tests__/directory and document the command inpackage.json.
Commit & Pull Request Guidelines
- Commit messages follow Conventional Commits based on history, e.g.,
chore: ...,docs: ...,refactor: .... - Keep PRs focused, include a short summary, and list commands run (e.g.,
npm run lint,npm run build). - Link related issues when applicable and describe any configuration changes (e.g., new env vars).
Security & Configuration Tips
- The server requires
SOLODIT_API_KEYin the environment; avoid committing keys. - The Solodit API rate limit is 20 requests per 60 seconds; consider pagination and backoff.
- Node.js 18+ is required for local development.
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 · 43 lines · 541 tokens per session scan A 82ec82262081
solodit-mcp AGENTS.md is an instructions file published in the GitHub repository zerotrust-labs/solodit-mcp (0 stars, last pushed 7mo ago), licensed MIT. It adds 541 tokens to every session, about $0.0027 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.