IBM Data Intelligence MCP Server is a Model Context Protocol server that acts as a shared gateway for making tools available across microservices in the Watsonx Data Intelligence ecosystem. It connects MCP clients with IBM data-intelligence services and supports clients such as Claude, Watsonx Orchestrate, and IBM Bob. The catalogue lists five skills for working with the server.
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 IBM/data-intelligence-mcp-server --skill mdi-job-controlgit clone --depth 1 https://github.com/IBM/data-intelligence-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/ibm/data-intelligence-mcp-server/mdi-job-control)<a href="https://agentmods.dev/skills/ibm/data-intelligence-mcp-server/mdi-job-control"><img src="https://agentmods.dev/badge/skills/ibm/data-intelligence-mcp-server/mdi-job-control/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/ibm/data-intelligence-mcp-server/mdi-job-control"><img src="https://agentmods.dev/badge/skills/ibm/data-intelligence-mcp-server/mdi-job-control.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.00056 | $0.01215 |
| Opus 5.5 | $0.00022 | $0.00486 |
| Sonnet 5.5 | $0.00011 | $0.00243 |
| Haiku 4.5 | $0.00006 | $0.00121 |
Grade A, and why
mdi-job-control 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 22d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MDI Job Control Guide
Overview
Use this skill when the user wants to control the lifecycle of an active metadata import job run — specifically to pause, resume, or cancel it. Detect the user's intent and guide them through the correct action using the pause_resume_or_cancel_mdi_job_run tool.
Typical user queries: "Pause my metadata import job", "Resume the import I paused earlier", "Cancel the running MDI job in my project", "Stop the import job for the Finance MDI".
Phase 0: Intent Detection
- Identify which action the user wants: pause, resume, or cancel.
- Identify which metadata import (MDI) and project the user is referring to.
- If the user's intent is unclear, ask them directly: "Do you want to pause, resume, or cancel the job run?"
- If the action is cancel, note that this is permanent and irreversible — you must confirm with the user before proceeding (Phase 2).
- If the action is pause or resume, you can proceed to Phase 1 once the project and MDI are identified.
Phase 1: Resolve the Project and MDI
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.
- 22d ago First seen · 95 lines · 56 tokens per session scan A 27d42e141a71
mdi-job-control is a skill published in the GitHub repository IBM/data-intelligence-mcp-server (20 stars, last pushed 9d ago), licensed Apache-2.0. It adds 56 tokens to every session and 1,215 once invoked, about $0.0002 per session on Opus 5.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-09-25.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…