Borrowing it
Nothing to install: this file belongs to mister-good-deal/host-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/mister-good-deal/host-mcp-jenkins/main/.github/instructions/add-jenkins-feature.instructions.mdgit clone --depth 1 https://github.com/mister-good-deal/host-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/mister-good-deal/host-mcp-jenkins/add-jenkins-feature)<a href="https://agentmods.dev/instructions/mister-good-deal/host-mcp-jenkins/add-jenkins-feature"><img src="https://agentmods.dev/badge/instructions/mister-good-deal/host-mcp-jenkins/add-jenkins-feature/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/mister-good-deal/host-mcp-jenkins/add-jenkins-feature"><img src="https://agentmods.dev/badge/instructions/mister-good-deal/host-mcp-jenkins/add-jenkins-feature.svg" alt="Reviewed on agentmods" width="80" 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.01478 | $0.01478 |
| Opus 5 | $0.00739 | $0.00739 |
| Sonnet 5 | $0.00296 | $0.00296 |
| Haiku 4.5 | $0.00148 | $0.00148 |
Grade A, and why
host-mcp-jenkins add-jenkins-feature.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 12d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adding a New Jenkins API Feature
Procedure for adding a new MCP tool that maps to a specific Jenkins REST API endpoint.
Prerequisites
- Identify the target Jenkins REST API endpoint (e.g.,
GET /job/{name}/api/json) - Determine the HTTP method (
GET,POST) and expected response format - Check the Jenkins API documentation:
- Remote Access API: https://www.jenkins.io/doc/book/using/remote-access-api/
- Jenkins Javadoc: https://javadoc.jenkins.io/
- Determine which tool category the feature belongs to:
- core (
src/tools/core.ts) — Jobs, builds, queue, triggers, status - logs (
src/tools/logs.ts) — Build console output and log search - scm (
src/tools/scm.ts) — Source control configurations and change sets - tests (
src/tools/tests.ts) — Test results and flaky test analysis
- core (
Step-by-Step Procedure
1. Define TypeScript Types
Add response interfaces in src/jenkins/types.ts for the Jenkins API response structure.
// Example: Adding a new type for a Jenkins plugin API response
export interface JenkinsPluginInfo {
shortName: string;
longName: string;
version: string;
active: boolean;
enabled: boolean;
url?: string;
[key: string]: unknown; // Allow extra fields from Jenkins
}
Tip: Use
[key: string]: unknownon interfaces to handle extra fields Jenkins may return.
2. Register the Tool
Add the tool registration in the appropriate src/tools/{category}.ts file. Follow the existing pattern:
/*
* ── getPlugins ──────────────────────────────────────────────────────
* Jenkins API: GET /pluginManager/api/json
* @see https://javadoc.jenkins.io/hudson/PluginManager.html
*/
server.registerTool(
"getPlugins",
{
description: "Get a list of installed Jenkins plugins",
inputSchema: {
// Define input parameters using Zod schemas
active: z.boolean().default(true).optional()
.describe("Filter to only active plugins")
},
annotations: { readOnlyHint: true } // Set to false for write operations
},
async({ active = true }) => {
logger.debug(`getPlugins: active=${active}`);
try {
const data = await client.get<JenkinsPluginList>(
"/pluginManager/api/json",
{ tree: "plugins[shortName,longName,version,active,enabled,url]" }
);
const plugins = active
? data.plugins.filter(p => p.active)
: data.plugins;
return toMcpResult(toolSuccess(plugins));
} catch (error) {
if (error instanceof JenkinsClientError && error.statusCode === 404) {
return toMcpResult(toolNotFound("Plugin Manager", ""));
}
return toMcpResult(toolError(error));
}
}
);
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.
- 12d ago First seen · 181 lines · 1,478 tokens per session scan A 2e976d0a9b3e
host-mcp-jenkins add-jenkins-feature.instructions.md is an instructions file published in the GitHub repository mister-good-deal/host-mcp-jenkins (1 stars, last pushed 6mo ago), licensed MIT. It adds 1,478 tokens to every session, about $0.0074 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
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.
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.
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).
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).