Borrowing it
Nothing to install: this file belongs to techskies11/datadog-mcp. 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/techskies11/datadog-mcp/main/.cursor/skills/mcp-tool-creator/SKILL.mdgit clone --depth 1 https://github.com/techskies11/datadog-mcpWrote 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/techskies11/datadog-mcp/mcp-tool-creator)<a href="https://agentmods.dev/skills/techskies11/datadog-mcp/mcp-tool-creator"><img src="https://agentmods.dev/badge/skills/techskies11/datadog-mcp/mcp-tool-creator/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/techskies11/datadog-mcp/mcp-tool-creator"><img src="https://agentmods.dev/badge/skills/techskies11/datadog-mcp/mcp-tool-creator.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.00036 | $0.02101 |
| Opus 5 | $0.00018 | $0.01051 |
| Sonnet 5 | $0.00007 | $0.00420 |
| Haiku 4.5 | $0.00004 | $0.00210 |
Grade A, and why
mcp-tool-creator 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 9d 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 — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Tool Creator
This skill guides you through creating new MCP tools for the Datadog MCP server with proper typing, documentation, and architecture.
Step-by-Step Tool Creation
Step 1: Plan the Tool
Before writing code, determine:
- Purpose: What specific task does this tool accomplish?
- API Endpoint: Which Datadog API endpoint(s) will it use?
- Parameters: What inputs does it need?
- Return Type: What data structure will it return?
- Domain: Which tool file should contain it? (logs, metrics, dashboards, apm, monitors, or new domain)
Step 2: Define TypedDict Response Structure
Create explicit types before implementation:
from typing import TypedDict, NotRequired
class ToolResponse(TypedDict):
"""Response from the new tool."""
success: bool
error: NotRequired[str]
# Add specific fields for your tool
data: list[DataItem]
count: int
next_cursor: NotRequired[str | None]
Step 3: Create Internal Implementation
In the appropriate tools/*.py file:
"""Module docstring describing this domain."""
from typing import TypedDict, Literal, NotRequired
from datadog_api_client.v2.api.relevant_api import RelevantApi
from datadog_api_client.v2.model.request_model import RequestModel
from ..auth import DatadogAuth
from ..utils.response import ResponseBuilder, format_error_response
from ..utils.auth import get_api_instance
# Define response types first
class ItemData(TypedDict):
"""Individual item in response."""
id: str
name: str
value: int
class ToolResponse(TypedDict):
"""Complete tool response."""
success: bool
data: list[ItemData]
count: int
error: NotRequired[str]
# Implementation function
def my_new_tool(
param1: str,
param2: int | None = None,
auth: DatadogAuth | None = None
) -> ToolResponse:
"""Internal implementation with business logic.
Args:
param1: Description of parameter 1
param2: Description of parameter 2 (optional)
auth: DatadogAuth instance (injected)
Returns:
ToolResponse with data and metadata
"""
# Get API instance
api_instance, auth = get_api_instance(RelevantApi, auth)
try:
# Build API request
request = RequestModel(
param1=param1,
param2=param2
)
# Call API
response = api_instance.call_endpoint(body=request)
# Format data
items: list[ItemData] = []
if hasattr(response, 'data') and response.data:
for item in response.data:
items.append({
"id": item.id if hasattr(item, 'id') else "",
"name": item.name if hasattr(item, 'name') else "",
"value": item.value if hasattr(item, 'value') else 0
})
# Use ResponseBuilder for auto-truncation
return ResponseBuilder.success("data", items)
except Exception as e:
return format_error_response("data", e)
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.
- 9d ago First seen · 340 lines · 36 tokens per session scan A 8023cc7f6d23
mcp-tool-creator is a skill published in the GitHub repository techskies11/datadog-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 2,101 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…