Borrowing it
Nothing to install: this file belongs to lewing/helix.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/lewing/helix.mcp/main/.squad/skills/mcp-wire-format-trim/SKILL.mdgit clone --depth 1 https://github.com/lewing/helix.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/lewing/helix.mcp/mcp-wire-format-trim)<a href="https://agentmods.dev/skills/lewing/helix.mcp/mcp-wire-format-trim"><img src="https://agentmods.dev/badge/skills/lewing/helix.mcp/mcp-wire-format-trim/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/lewing/helix.mcp/mcp-wire-format-trim"><img src="https://agentmods.dev/badge/skills/lewing/helix.mcp/mcp-wire-format-trim.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.00000 | $0.03970 |
| Opus 5 | $0.00000 | $0.01985 |
| Sonnet 5 | $0.00000 | $0.00794 |
| Haiku 4.5 | $0.00000 | $0.00397 |
Grade A, and why
mcp-wire-format-trim 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.
How it starts
The opening of the file, as written. The whole thing — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Wire-Format Trim
When to use
- You need to reduce
tools/listtoken/byte cost without changing tool behavior. - You are auditing MCP metadata bloat in
McpServerToolattributes or auto-generated schemas.
Pattern 1: default-annotation audit
- Verify SDK defaults from the exact package version in use (
ModelContextProtocol.Coresource or reflection). - Only remove attribute properties whose explicit value matches the SDK default.
- In SDK 1.3.0, the important defaults are:
OpenWorld = trueReadOnly = falseIdempotent = falseDestructive = trueUseStructuredContent = false
- Consequence:
OpenWorld=trueis removable noise, butDestructive=falsemust stay.
Pattern 2: drop outputSchema while preserving wire payload
Use this only for tiny results where schema carries little value and you must keep the actual tool-call payload stable.
- Change the tool method return type to
CallToolResult(orTask<CallToolResult>). - Remove
UseStructuredContent = truefrom the[McpServerTool]attribute so the SDK stops advertisingoutputSchema. - Return
CallToolResultmanually with both:Content = [new TextContentBlock { Text = JsonSerializer.Serialize(value, McpJsonUtilities.DefaultOptions) }]StructuredContent = JsonSerializer.SerializeToElement(value, McpJsonUtilities.DefaultOptions)
- This keeps the tool-call JSON payload/structured content intact while shrinking
tools/list.
Pattern 2b: minimal object outputSchema via an empty marker type (SDK 2.x)
Use when a tool must keep UseStructuredContent = true — because SDK 2.x picks the
structuredContent envelope from the schema's objectness — but the detailed schema is not worth
its fixed-context rent.
The rule that makes this safe: AIFunctionMcpServerTool.ShouldWrapValueForLegacyWire asks only
whether the schema's type is object (or ["object","null"]). It never reads properties or
required, and the C# SDK does no runtime validation of structuredContent against outputSchema.
So {"type":"object"} is functionally equivalent to a full property mirror, at ~17 B instead of
hundreds.
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 · 278 lines · 0 tokens per session scan A ee1ddafe7ff9
mcp-wire-format-trim is a skill published in the GitHub repository lewing/helix.mcp (4 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,970 tokens. 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
diagrams
Mermaid diagrams following the C4 model: context, container, component, sequence, ER and deployment. Use when saying "diagram", "visualize", or "architecture diagram".
e2e
Generate and run Playwright E2E tests traced to spec.md acceptance criteria, with an optional accessibility audit. Use when saying "e2e tests" or "a11y audit".
release-expert
Multi-repo release coordination: version alignment, RC lifecycle, release waves, rollback planning. Use when saying "release", "version alignment", or "cut an RC".
tdd-cycle
Execute full TDD red-green-refactor cycle with validation gates. Use when saying "TDD cycle", "test-driven development", or "full TDD workflow".
debug
Systematic 4-phase debugging with escalation protocol. Use when saying "debug", "investigate bug", "find root cause", "why is this failing", or "fix this bug".
increment
Plan a unit of work as a SpecWeave increment - spec.md with Problem, Scope, numbered ACs and an Approach, plus tasks.md. Use when starting a feature, bug, hotfix or refactor.