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/olssonsten/mcp-redmine/agents-mdgit clone --depth 1 https://github.com/olssonsten/mcp-redmineWrote 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/olssonsten/mcp-redmine/agents-md)<a href="https://agentmods.dev/instructions/olssonsten/mcp-redmine/agents-md"><img src="https://agentmods.dev/badge/instructions/olssonsten/mcp-redmine/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.00412 | $0.00412 |
| Opus 5 | $0.00206 | $0.00206 |
| Sonnet 5 | $0.00082 | $0.00082 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
mcp-redmine 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.
What it actually says
AGENTS.md
This file provides guidance to agents when working with code in this repository.
Build/Test Commands
make test- Run tests using uv with dev dependencies (not standard pytest)make test-coverage- Generate HTML coverage reports in htmlcov/uv sync --group dev- Install dev dependencies (required before testing)uv run --group dev pytest tests/ -v- Direct test execution with uv
Project-Specific Patterns
- Environment Variables Required: REDMINE_URL and REDMINE_API_KEY must be set or server fails to start
- Response Filtering Architecture: All API responses go through apply_response_filter() with backward compatibility fallback
- Filter Presets: Use string preset names ("minimal", "clean", "essential_issues") that get converted to dict configs
- Error Handling Pattern: All tools return YAML with {status_code, body, error} structure, never raise exceptions
- File Path Requirements: Upload/download tools require fully qualified absolute paths, not relative paths
- OpenAPI Integration: redmine_openapi.yml is loaded at startup and used for path validation and MCP capabilities
Critical Implementation Details
- Filtering Fallback: If mcp_filter processing fails, original response is returned (lines 99-102 in server.py)
- Version Sync: VERSION constant in server.py must match pyproject.toml version for releases
- MCP Tool Decoration: All tools use @mcp.tool() decorator and return YAML strings, not Python objects
- Custom Fields Handling: Special filtering logic for custom_fields arrays based on field names
- Content-Type Switching: Upload tool switches to 'application/octet-stream' for file uploads
Testing Requirements
- Tests must use pytest with uv run wrapper
- All filtering tests verify backward compatibility
- Response filter tests check both success and error scenarios
- Preset tests validate all presets work with actual filtering system
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 · 30 lines · 412 tokens per session scan A 5f53a065b663
mcp-redmine AGENTS.md is an instructions file published in the GitHub repository olssonsten/mcp-redmine (1 stars, last pushed 11mo ago), licensed MPL-2.0. It adds 412 tokens to every session, about $0.0021 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other instructions, from other repositories
ESAA-Core AGENTS.md
Instructions for elzobrito/ESAA-Core, covering agents.md — contrato operacional codex/esaa, 1. autoridade e termos, 2. cli e runner, ou configure o runner uma vez por sessão and 3. concorrência.
idd-skill idd-resume.instructions.md
Instructions for kurone-kito/idd-skill, covering idd — resume phase, required inputs, step 0 — route classifier, operator-present release and step 1 — identify claim state.
tmetric-minimal-mcp CLAUDE.md
Claude Code instructions for guglielmo/tmetric-minimal-mcp, covering claude.md, development commands, project architecture, file structure and core architecture patterns.
shelly-forge CLAUDE.md
Claude Code instructions for mslavov/shelly-forge, covering documentation usage guidelines, critical: framework-first reading order, 📚 mandatory reading order, pre-task protocol and post-task protocol.
vibelive AGENTS.md
AGENTS.md instructions for pooriaarab/vibelive, covering agents.md, repository context, pull requests, cloud agents (cursor) and install & test.
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).