Borrowing it
Nothing to install: this file belongs to dockndevai/mcp-azure-devops. 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/dockndevai/mcp-azure-devops/main/.claude/skills/mcp-suite-maintenance/SKILL.mdgit clone --depth 1 https://github.com/dockndevai/mcp-azure-devopsWrote 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/dockndevai/mcp-azure-devops/mcp-suite-maintenance)<a href="https://agentmods.dev/skills/dockndevai/mcp-azure-devops/mcp-suite-maintenance"><img src="https://agentmods.dev/badge/skills/dockndevai/mcp-azure-devops/mcp-suite-maintenance/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/dockndevai/mcp-azure-devops/mcp-suite-maintenance"><img src="https://agentmods.dev/badge/skills/dockndevai/mcp-azure-devops/mcp-suite-maintenance.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.00112 | $0.01650 |
| Opus 5 | $0.00056 | $0.00825 |
| Sonnet 5 | $0.00022 | $0.00330 |
| Haiku 4.5 | $0.00011 | $0.00165 |
Grade A, and why
mcp-suite-maintenance 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 10d 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 mcp-suite-maintenance — 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintaining the MCP server suite
These six TypeScript MCP servers share one architecture and one security philosophy: safe by default, least privilege, never leak secrets. This skill captures the invariants and the routine tasks so changes stay consistent and safe.
Shared architecture (every repo)
src/
index.ts # stdio entrypoint: load config → build server → connect
server.ts # registers ONLY tools whose capability ≤ access mode
config.ts # env → typed config (connection + security)
security.ts # PURE policy engine (SecurityPolicy). No I/O. Unit-tested.
<domain>/client.ts # thin wrapper over the real SDK/REST API
tools/{read,write,admin}.ts # tool defs tagged with a capability
test/ # vitest — always includes security.test.ts
- Capabilities: every tool declares
capability: "read" | "write" | "admin". - Access modes:
read-only(0) →read-write(1) →admin(2). A tool is only registered whenCAPABILITY_RANK[tool] <= MODE_RANK[mode]. Over-privileged tools are never advertised — this is the primary guarantee. - Guard at call time too: every handler calls
policy.guard({ tool, capability, <resource>, destructive? })before doing work. Defence in depth on top of registration.
Non-negotiable invariants (do NOT regress these)
- Read-only means read-only. A tool tagged
readmust never mutate. If it can mutate, it iswriteoradmin. - Destructive ops need a second opt-in. Deletes/drops require the mode and an explicit flag (
*_ALLOW_DELETE,OCI_ALLOW_APPLY,K8S_ALLOW_EXEC, etc.). The most dangerous (k8sexec_in_pod) is not even registered without its flag. - Protected resources are read-only forever. System realms/namespaces/databases/internal topics can be read but never mutated, regardless of mode.
- Secrets never reach the model. Redact before returning (see
redact.tsin mcp-oci / mcp-debezium;reset_passwordnever echoes;list_clientsstrips secrets; ClickHouse caps rows). Any new field that could carry a credential must be redacted. - Audit + dry-run apply to every write.
guard()emits the audit line and returns{ dryRun }; write handlers must honordryRunby returning intent without calling the backend. - stdout belongs to MCP. All logs/audit/warnings go to stderr only. Never
console.logto stdout.
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.
- 10d ago First seen · 84 lines · 112 tokens per session scan A f5e81688a5ec
mcp-suite-maintenance is a skill published in the GitHub repository dockndevai/mcp-azure-devops (1 stars, last pushed today), licensed MIT. It adds 112 tokens to every session and 1,650 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to mcp-suite-maintenance, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
blast-radius
Trace ServiceNow configuration dependencies — what artifacts touch a given field, what calls a script include, table/app-level config inventory. Use before deletes, renames, or refactors.
change-management
Create and transition ServiceNow change requests (normal/standard/emergency), change tasks, affected CIs, approval routing, CAB scheduling, and conflict detection across maintenance windows.
cmdb-patterns
Create ServiceNow CIs and cmdbrelci relationships, walk upstream/downstream impact, detect orphan/stale CIs, and align discovered CIs with the proper sysclassname hierarchy.
incident-management
Manage ServiceNow incidents — creation with impact/urgency priority calc, auto-assignment by category, reassignment tracking, major incident declaration with bridge calls, time-based escalation, MTTR metrics.
client-scripts
Write ServiceNow client scripts (onLoad/onChange/onSubmit/onCellEdit) using gform, guser, GlideAjax, field visibility/mandatory toggles, and validation with debounced server calls.
fluent-development
This skill should be used when the user asks to "build a fluent app", "create a servicenow app in typescript", or mentions "servicenow sdk", "now-sdk", "fluent", "scoped app as code", or "pro-code development" — or when the working directory contains a now.config.json or .now.ts files.