Borrowing it
Nothing to install: this file belongs to lanbaoshen/mcp-jenkins. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lanbaoshen/mcp-jenkins/master/AGENTS.mdgit clone --depth 1 https://github.com/lanbaoshen/mcp-jenkinsWrote 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/lanbaoshen/mcp-jenkins/agents-md)<a href="https://agentmods.dev/instructions/lanbaoshen/mcp-jenkins/agents-md"><img src="https://agentmods.dev/badge/instructions/lanbaoshen/mcp-jenkins/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.1 | $0.00856 | $0.00856 |
| Opus 5 | $0.00428 | $0.00428 |
| Sonnet 5 | $0.00171 | $0.00171 |
| Haiku 4.5 | $0.00086 | $0.00086 |
Grade A, and why
mcp-jenkins 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 8d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mcp-jenkins
Bridges Jenkins CI with AI language models via Anthropic's Model Context Protocol (MCP). Jenkins operations are exposed as MCP tools that LLM clients invoke.
Build and Test
# Install (requires uv)
uv sync --group dev
# Run tests with coverage
uv run pytest --cov=src
# Lint and format
uv run ruff check .
uv run ruff format .
# Pre-commit (runs tests + ruff)
pre-commit run --all-files
Architecture
src/mcp_jenkins/
├── __init__.py # CLI entry point (click)
├── core/ # Lifespan context + ASGI auth middleware
├── jenkins/ # Jenkins REST client + URL templates + Pydantic models
└── server/ # MCP tool definitions (@mcp.tool decorators)
Credential resolution (in core/lifespan.py): session singleton cache → HTTP request headers (x-jenkins-url, x-jenkins-username, x-jenkins-password) → env vars set from CLI args. Always call jenkins(ctx) inside tool functions to obtain the client; never instantiate Jenkins directly.
Read-only mode: Tools that mutate Jenkins state must carry tags=['write']. Tools tagged 'read' remain available when --read-only is passed. Every new tool must have exactly one of these two tags.
Conventions
Adding a new MCP tool
- Add the function in the appropriate
server/*.pymodule (or create a new module and import it inserver/__init__.py). - Decorate with
@mcp.tool(tags=['read'])or@mcp.tool(tags=['write']). - First argument must be
ctx: Context; all subsequent arguments are keyword-only domain params. - Return
model.model_dump(exclude_none=True)(or alist/dictof such). - Use
jenkins(ctx)to get the Jenkins client — never store it in module-level state.
from mcp_jenkins.server import mcp
from mcp_jenkins.core import jenkins
@mcp.tool(tags=['read'])
async def get_something(ctx: Context, fullname: str) -> dict:
"""Short description.
Args:
ctx: MCP context.
fullname: Full job name, e.g. "folder/job".
Returns:
Serialised model dict.
"""
return jenkins(ctx).get_something(fullname=fullname).model_dump(exclude_none=True)
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.
- 8d ago First seen · 91 lines · 856 tokens per session scan A 0d01638c6a79
mcp-jenkins AGENTS.md is an instructions file published in the GitHub repository lanbaoshen/mcp-jenkins (148 stars, last pushed today), licensed MIT. It adds 856 tokens to every session, about $0.0043 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
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.
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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).
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.