Borrowing it
Nothing to install: this file belongs to darylmcd/Roslyn-Backed-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/darylmcd/Roslyn-Backed-MCP/main/.claude/skills/surface-audit/SKILL.mdgit clone --depth 1 https://github.com/darylmcd/Roslyn-Backed-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/darylmcd/roslyn-backed-mcp/surface-audit)<a href="https://agentmods.dev/skills/darylmcd/roslyn-backed-mcp/surface-audit"><img src="https://agentmods.dev/badge/skills/darylmcd/roslyn-backed-mcp/surface-audit/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/darylmcd/roslyn-backed-mcp/surface-audit"><img src="https://agentmods.dev/badge/skills/darylmcd/roslyn-backed-mcp/surface-audit.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.00118 | $0.01692 |
| Opus 5 | $0.00059 | $0.00846 |
| Sonnet 5 | $0.00024 | $0.00338 |
| Haiku 4.5 | $0.00012 | $0.00169 |
Grade A, and why
surface-audit 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
surface-audit
Cross-check the live server surface against every hard-coded count in the repo's documentation.
Motivation
The 2026-04-10→04-24 retro showed multiple self-audit sessions spending significant grep budget verifying doc claims like "10 skills", "66 stable + 60 experimental = 126 tools", "123 tools". This skill does that walk in one pass so agents get an authoritative drift report without polluting the transcript.
Steps
1. Collect live surface
Call mcp__roslyn__server_info. Record from the response:
surface.tools.stable,surface.tools.experimental,surface.registered.toolssurface.resources.stable,surface.resources.experimental,surface.registered.resourcessurface.prompts.stable,surface.prompts.experimental,surface.registered.promptsversion,catalogVersion,surface.registered.parityOk
2. Count shipped skills on disk
Glob skills/*/SKILL.md — the count is the live skill count. Record as shippedSkills.
3. Count maintainer-only skills
Glob .claude/skills/*/SKILL.md — these are the repo-local override skills (not shipped). Record as maintainerSkills. Report the totals but DO NOT compare against shipped-skill count claims (they're separate surfaces).
4. Sweep docs for numeric surface claims
Grep for patterns that match surface count claims. Regex list (case-insensitive):
[0-9]+\s*(stable|experimental)?\s*(tools?|resources?|prompts?|skills?)
Scope the grep to:
README.mddocs/**/*.mdai_docs/**/*.md(skipai_docs/archive/**andai_docs/reports/**— historical snapshots, drift expected)CHANGELOG.md— ONLY the## [Unreleased]section; shipped version sections are frozen history.claude-plugin/plugin.json+.claude-plugin/marketplace.json— description strings
For each hit, capture: file, line, the exact claim text, the claimed count.
5. Compute drift
Produce a table:
| Claim source | Claim text (excerpt) | Claimed | Live | Drift |
|---|---|---|---|---|
docs/setup.md:42 |
"107 stable tools and 54 experimental" | 107 / 54 | 107 / 54 | ok |
README.md:18 |
"over 150 Roslyn-powered tools" | 150 | 161 | ok (+11 live, claim is conservative) |
ai_docs/references/tool-usage.md:9 |
"...10 shipped skills..." | 10 | 12 | drift +2 |
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 · 123 lines · 118 tokens per session scan A 174859ae4977
surface-audit is a skill published in the GitHub repository darylmcd/Roslyn-Backed-MCP (1 stars, last pushed today), licensed MIT. It adds 118 tokens to every session and 1,692 once invoked, about $0.0006 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.