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 neverinfamous/mysql-mcp --skill service-remappinggit clone --depth 1 https://github.com/neverinfamous/mysql-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/neverinfamous/mysql-mcp/service-remapping)<a href="https://agentmods.dev/skills/neverinfamous/mysql-mcp/service-remapping"><img src="https://agentmods.dev/badge/skills/neverinfamous/mysql-mcp/service-remapping.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.00068 | $0.04587 |
| Opus 5 | $0.00034 | $0.02294 |
| Sonnet 5 | $0.00014 | $0.00917 |
| Haiku 4.5 | $0.00007 | $0.00459 |
Grade A, and why
service-remapping 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 7d 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.
This is a copy
100% identical to service-remapping — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 440 lines — stays where its author put it; the contents beside it link to each section on GitHub.
APM Service Remapping
Before acting: Surface an impact preview (monitors/dashboards referencing the old service name) before presenting the planned rule. For inferred-entity remaps, also confirm
peer.serviceis set on outbound spans. Variables from## Context to resolve before actingcan be gathered alongside that preview rather than blocking it.
How Service Remapping Works — Domain Knowledge
Read this before building any rule. It gives you the mental model to construct the right filter and catch edge cases.
What remapping does: A rule intercepts telemetry at ingestion time and rewrites the service name before indexing. A rule says: "for any entity matching this filter, replace its service name with this new value."
Two entity types — pick the right one:
| Entity type | rule_type integer |
What it targets |
|---|---|---|
| SERVICE | 0 |
Instrumented services — have spans with an explicit service tag set by a tracer |
| INFERRED_ENTITY | 1 |
Auto-detected from outbound calls — named from peer.service. Requires peer.service to be set on outbound spans (see prerequisite below). |
Prerequisite for inferred entity remapping — peer.service must be set:
Inferred entity remapping only works when the tracer sets peer.service on outbound spans. Without it, entities are keyed by peer.hostname and remapping rules will not apply.
To enable this, set the following env var on the instrumented service (not the downstream dependency):
DD_TRACE_PEER_SERVICE_DEFAULTS_ENABLED=true
This makes the ddtrace tracer automatically propagate peer.service from peer.hostname on outbound HTTP, gRPC, and database calls. Without this, pup traces search will show spans with peer.hostname but no peer.service, and no service remapping rule will match.
To verify peer.service is being set before building a rule:
pup traces search --query "@peer.service:<ENTITY_NAME>" --from 15m --limit 5
If zero results — the tracer is not setting peer.service. Ask the user to add DD_TRACE_PEER_SERVICE_DEFAULTS_ENABLED=true to their service's environment and redeploy before continuing.
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.
- 7d ago First seen · 440 lines · 68 tokens per session scan A 23986548c73d
service-remapping is a skill published in the GitHub repository neverinfamous/mysql-mcp (10 stars, last pushed 7d ago), licensed MIT. It adds 68 tokens to every session and 4,587 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to service-remapping, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
dory
Use Dory as the official AI-native SQL workspace for agents. Use when the user asks to inspect or analyze databases, explore unknown schemas, debug data issues, run read-only SQL through Dory MCP, manage Dory Agent Runs, create or update SQL workspace tabs, work with saved queries, preserve query results, or hand SQL…
sqlike
Check SQL with sqlike — deterministic static analysis (validity, anti-patterns, rewrites, index advice) and query-equivalence verification. Use whenever you write, edit, review, or rewrite a SQL query, or need to prove two queries return the same results. Requires the sqlike MCP server (@sqlike/mcp) or the sqlike CLI…
haiku
When writing a haiku for this bot, follow these conventions.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
ln-62-repository-publisher
Commits, pushes, and remotely verifies authorized repository changes. Not for releases, package publication, or announcements.