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/azdo-rest-param-surface-audit/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/azdo-rest-param-surface-audit)<a href="https://agentmods.dev/skills/lewing/helix.mcp/azdo-rest-param-surface-audit"><img src="https://agentmods.dev/badge/skills/lewing/helix.mcp/azdo-rest-param-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/lewing/helix.mcp/azdo-rest-param-surface-audit"><img src="https://agentmods.dev/badge/skills/lewing/helix.mcp/azdo-rest-param-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.00028 | $0.01030 |
| Opus 5 | $0.00014 | $0.00515 |
| Sonnet 5 | $0.00006 | $0.00206 |
| Haiku 4.5 | $0.00003 | $0.00103 |
Grade A, and why
azdo-rest-param-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 8d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
Use when adding a new AzDO REST endpoint wrapper, or when auditing existing tools for missing capabilities. The symptom of a missing param is always the same: the parameter is accepted by the MCP binding layer (or CLI), but the value is silently ignored — indistinguishable from a successful call with the filter applied.
The Audit
For each AzDO MCP tool, compare:
- The AzDO REST API reference for that endpoint (query parameters available)
- The tool method signature (what MCP/CLI accepts)
- The URL construction in
AzdoApiClient(what actually reaches the server)
If a REST param exists but is absent from either the method or the URL construction, it is a bug.
Known Gaps (fixed 2026-06-24)
| Tool | REST param | Root cause |
|---|---|---|
azdo_builds |
minTime, maxTime |
Not in AzdoBuildFilter, not forwarded to URL |
azdo_builds |
queryOrder |
Hardcoded to queueTimeDescending, not exposed |
azdo_test_attachments |
$top |
Present in signature, not appended to URL |
azdo_test_results |
outcomes |
Hardcoded to Failed, not exposed |
AzDO Time Range Semantics
minTime and maxTime are not named after a specific field — the field
they filter is determined by queryOrder:
queueTimeDescending→ filters by queue timestartTimeDescending→ filters by start timefinishTimeDescending→ filters by finish time
Always document this coupling in the parameter description so callers know to pair them correctly.
Patterns
- Check
AzdoApiClientURL construction against the REST reference for every param accepted by the method signature. - Check
AzdoBuildFilterproperties againstListBuildsAsyncquery params. - Check cache keys (
HashFilter, per-endpoint key strings) to ensure every discriminating parameter is included. Missing a param → stale cache hit. - Add a test that calls the method with the new param set and asserts the
param appears in the captured URL (via
FakeHttpMessageHandler.LastRequest).
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.
- 8d ago First seen · 99 lines · 28 tokens per session scan A b17b2c3676d4
azdo-rest-param-surface-audit is a skill published in the GitHub repository lewing/helix.mcp (4 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 1,030 once invoked, about $0.0001 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
argot-suggest-rules
Turn a convention argot has already discovered into a scripted custom rule. Runs argot conventions, surfaces the repo's mined placement conventions (where a kind of code lives — "validation in schema files", "DB access only in migrations", "business logic in the service layer, not views") and internal-API vocabulary…
review
Adversarial fresh-context review of an increment before it ships. Every finding cites path:line and is re-verified. Use when saying "review", "grill this", or "critique the implementation".
sw-review
Adversarial fresh-context review of an increment before it ships; every finding cites path:line and is re-verified. Use for "review this", "critique the implementation", "review before closing".
csharp-dotnet
Use when writing, reviewing, testing, or shipping C# / .NET code — ASP.NET Core APIs (minimal APIs vs controllers), EF Core data access, async correctness, solution layout in .cs/.csproj/.sln. NOT a Java/Spring backend (that is spring-boot), NOT a Node/TypeScript backend (that is nestjs), NOT framework-neutral REST…
argot-setup
Set argot up for a repository end to end — audit its history, decide what should shape its voice, fit, verify the fit actually catches things, tune the rules its own history says are noisy, and wire the places it runs (pre-write hook, pre-commit, MCP, CI). One sitting, one decision at a time, each proposed with the…
argot-check
Score your working changes with argot — flag code foreign to this repo's own patterns (unfamiliar dependencies, APIs, constructs), functions the repo already has, code filed in the wrong place, imports that break the repo's layering, and tests weakened, disabled, or deleted alongside a production change — before…