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 skills add mdtahmidhossain/jenkins-http-mcp-server --skill jenkins-source-researchergit clone --depth 1 https://github.com/mdtahmidhossain/jenkins-http-mcp-serverWrote 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/skills/mdtahmidhossain/jenkins-http-mcp-server/jenkins-source-researcher)<a href="https://agentmods.dev/skills/mdtahmidhossain/jenkins-http-mcp-server/jenkins-source-researcher"><img src="https://agentmods.dev/badge/skills/mdtahmidhossain/jenkins-http-mcp-server/jenkins-source-researcher/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/skills/mdtahmidhossain/jenkins-http-mcp-server/jenkins-source-researcher"><img src="https://agentmods.dev/badge/skills/mdtahmidhossain/jenkins-http-mcp-server/jenkins-source-researcher.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.00029 | $0.00398 |
| Opus 5 | $0.00015 | $0.00199 |
| Sonnet 5 | $0.00006 | $0.00080 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
jenkins-source-researcher 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 11d 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
Jenkins Source Researcher
Research Jenkins behavior from the checked-out source, not memory.
Source
- Read
docs/source-truth.md, then usevendor/jenkinsat the exact tag and commit recorded there. - Verify with
git describe --tags --exact-matchandgit rev-parse HEADbefore relying on the checkout. - Cite file paths and line numbers in findings.
Search Patterns
Use rg first:
- Stapler API:
getApi,new Api,@WebMethod - POST endpoints:
@RequirePOST,@POST,doBuild,doBuildWithParameters,doStop,doDoDelete - Config:
doConfigDotXml,updateByXml,createItem - Logs/artifacts:
consoleText,progressiveText,getArtifacts,doArtifact - Workspace archives/state:
doWs,getSomeWorkspace,DirectoryBrowserSupport,*zip*,Item.WORKSPACE,isInQueue,getQueueItem,getLastBuild,isBuilding,isInProgress - Areas:
crumbIssuer,queue,computer,view,pluginManager,testReport
Classify Evidence
- Distinguish Jenkins core from plugin behavior.
- If evidence is in plugin docs or Javadoc, mark the feature plugin-dependent.
- If an endpoint is not proven, mark it unsupported rather than guessing.
- Record permission checks when discoverable, such as
checkPermission,hasPermission, or documented permission names.
Output
Summaries should include endpoint path, source file and line references, required permission if discoverable, and any unsupported or plugin-dependent caveat.
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.
- 11d ago First seen · 38 lines · 29 tokens per session scan A 7546493806bc
jenkins-source-researcher is a skill published in the GitHub repository mdtahmidhossain/jenkins-http-mcp-server (0 stars, last pushed 4d ago), licensed MIT. It adds 29 tokens to every session and 398 once invoked, about $0.0001 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 skills, from other repositories
python-guidelines
This skill should be used when writing, reviewing, or refactoring Python code. Covers code integration, idiomatic patterns, docstring formatting, anti-abstraction rules, and software engineering basics.
playwright-testing
E2E testing with Playwright - Page Objects, cross-browser, CI/CD.
jenkins-cicd
Jenkins CI/CD pipeline management — monitor builds, trigger pipelines, analyze logs, and track SCM changes for network automation workflows.
diagnosing-ci-and-merge-bottlenecks
Diagnoses CI and pull-request pipeline health for a GitHub repo using the engineering analytics MCP tools — pull-requests (PR list with CI status), workflow-health (per-workflow CI trends), and pr-lifecycle (a single PR's timeline). Use when asked whether CI is getting faster or slower, which GitHub Actions workflow…
investigating-ci-failures
Investigates a specific CI failure to a verdict: whose fault, which commit, who wrote it, and whether it's fixed. Use for "who broke master", "why did this test fail in CI", "is this failure my PR's fault or everyone's", "is this test flaky or actually broken", "when did this failure start". Works from the…
turning-engineering-analytics-into-insights
Converts engineering analytics (PR / CI) data into saved PostHog insights, dashboards, and subscriptions, and explains how to query the product data directly with SQL. Covers discovering per-team GitHub warehouse tables via engineering-analytics-sources, replicating curated column semantics in HogQL, reading exposed…