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/flor3z-github/redmine-mcp-server/agents-mdgit clone --depth 1 https://github.com/flor3z-github/redmine-mcp-serverWhat 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.01815 | $0.01815 |
| Opus 5 | $0.00907 | $0.00907 |
| Sonnet 5 | $0.00363 | $0.00363 |
| Haiku 4.5 | $0.00181 | $0.00181 |
Grade A, and why
redmine-mcp-server 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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- redmine-mcp-server AGENTS.md — 88% identical, 8 lines differ
How it starts
The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to Codex (Codex.ai/code) when working with code in this repository.
Branch Strategy: Development work should be done on the develop branch. Releases are created by merging develop to main.
Project Overview
This is a Model Context Protocol (MCP) server for Redmine integration, written in TypeScript using ES modules. It enables AI assistants to interact with Redmine project management systems through a comprehensive REST API integration.
Common Development Commands
Essential Commands
npm run build- Compile TypeScript to dist/npm run dev- Run development server with tsxnpm test- Run test suite with Vitestnpm run test:coverage- Run tests with coverage (requires 80% threshold)npm run lint- ESLint validation for TypeScript filesnpm run format- Format code with Prettiernpm run inspector- Start MCP Inspector for debugging tools
Testing Commands
npm test- Run all testsnpm run test:coverage- Run with coverage reports (80% requirement)- Individual test files can be run with:
npx vitest src/path/to/test.ts
Git Branching Strategy
This project uses a Git Flow branching model with two main branches:
Branch Structure
mainbranch: Production-ready code, triggers releasesdevelopbranch: Integration branch for features (default branch)
Development Workflow
Daily Development (on develop branch):
npm run lint- Check code stylenpm run test- Ensure tests passnpm run build- Verify build succeeds- Push to
developbranch for CI validation
Release Workflow (from develop to main):
- Create Pull Request from
developtomain - Review and merge PR to trigger release
- Automated release publishes to NPM
CI/CD Workflow Monitoring
Monitor workflows based on the branch you're working with:
Commands for Monitoring
- Check workflow status:
gh run list --repo flor3z-github/redmine-mcp-server --limit 3 - Watch active workflow:
gh run watch <run-id> --repo flor3z-github/redmine-mcp-server - View failed logs:
gh run view --log-failed --job=<job-id> --repo flor3z-github/redmine-mcp-server - Monitor workflow URL: https://github.com/flor3z-github/redmine-mcp-server/actions
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.
- 3d ago First seen · 197 lines · 1,815 tokens per session scan A b1cc50490aa7
redmine-mcp-server AGENTS.md is an instructions file published in the GitHub repository flor3z-github/redmine-mcp-server (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 1,815 tokens to every session, about $0.0091 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.