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/guigui42/mcp-vosdroits/documentationgit clone --depth 1 https://github.com/guigui42/mcp-vosdroitsWrote 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/guigui42/mcp-vosdroits/documentation)<a href="https://agentmods.dev/instructions/guigui42/mcp-vosdroits/documentation"><img src="https://agentmods.dev/badge/instructions/guigui42/mcp-vosdroits/documentation.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.00836 | $0.00836 |
| Opus 5 | $0.00418 | $0.00418 |
| Sonnet 5 | $0.00167 | $0.00167 |
| Haiku 4.5 | $0.00084 | $0.00084 |
Grade A, and why
mcp-vosdroits documentation.instructions.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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Standards
Code Documentation
General Principles
- Prioritize self-documenting code through clear naming
- Document all exported symbols (types, functions, methods, constants)
- Start documentation with the symbol name
- Write documentation in English
- Write complete sentences
Package Documentation
- Add package comment at the top of one file in the package
- Start with "Package [name]"
- Explain the package's purpose and main functionality
- Include usage examples when helpful
Example:
// Package tools provides MCP tool implementations for searching
// French public service information from service-public.gouv.fr.
package tools
Function Documentation
- Document what the function does, not how it does it
- Include parameter descriptions when not obvious
- Document return values, especially errors
- Mention any side effects or special behavior
Example:
// SearchProcedures searches for procedures on service-public.gouv.fr
// matching the given query. It returns up to limit results.
// Returns an error if the HTTP request fails or the response is invalid.
func SearchProcedures(ctx context.Context, query string, limit int) ([]Result, error)
Type Documentation
- Document the purpose of the type
- Explain important fields if not obvious
- Document JSON/JSONSCHEMA tags meaning when complex
Constant Documentation
- Document groups of related constants
- Explain the purpose and valid values
README Documentation
Required Sections
-
Project Title and Description
- Clear, concise description of what the project does
-
Installation
- How to install/build the project
- Prerequisites and dependencies
-
Usage
- Quick start guide
- Basic examples
- Common use cases
-
Configuration
- Environment variables
- Configuration file format
- Default values
-
API/Tool Documentation
- List of available MCP tools
- Input/output schemas
- Example requests/responses
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 · 152 lines · 836 tokens per session scan A f4942f4e8718
mcp-vosdroits documentation.instructions.md is an instructions file published in the GitHub repository guigui42/mcp-vosdroits (105 stars, last pushed 6mo ago), licensed MIT. It adds 836 tokens to every session, about $0.0042 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
ollama CLAUDE.md
Claude Code instructions for ollama/ollama: See AGENTS.md for the shared agent instructions for this repository.
azure-sdk-for-go go-code.instructions.md
Instructions for Azure/azure-sdk-for-go: All code should follow the guidelines from the Azure Go SDK Guidelines. This document is a summary of the most important guidelines to follow when contributing to the Azure Go SDK.
gorest AGENTS.md
AGENTS.md instructions for pilinux/gorest, covering agents.md, project overview, build and run commands, build and tidy dependencies.
chatgpt-cli CLAUDE.md
Claude Code instructions for kardolus/chatgpt-cli, covering chatgpt-cli — release runbook, prerequisites, 1. cut the release, 2. publish the github release + binaries and 3. update the homebrew tap.
kessoku AGENTS.md
AGENTS.md instructions for mazrean/kessoku, covering repository guidelines — kessoku, project structure, common commands, build and test.
ketch CLAUDE.md
Claude Code instructions for 1broseidon/ketch, covering ketch, architecture, build & test, output format and output flags (all commands).