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 agentmods add skills/lewing/helix.mcp/helix-clinpx skills add lewing/helix.mcp --skill helix-cligit 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/helix-cli)<a href="https://agentmods.dev/skills/lewing/helix.mcp/helix-cli"><img src="https://agentmods.dev/badge/skills/lewing/helix.mcp/helix-cli.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 | $0.00113 | $0.01789 |
| Opus 5 | $0.00056 | $0.00894 |
| Sonnet 5 | $0.00023 | $0.00358 |
| Haiku 4.5 | $0.00011 | $0.00179 |
Grade A, and why
helix-cli 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 5d 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.
Helix CLI
Investigate Helix and Azure DevOps CI failures with hlx when you want shell pipelines, --json, and jq without loading the MCP toolset into context.
When to Use This Skill
Use this skill when:
- You want
hlx describeas the fastest first step to understand which MCP-equivalent investigation commands exist before drilling into help or schemas. - Helix/AzDO MCP tools are not loaded, but
hlxis installed or available viadotnet run. - You want to script investigations with shell pipelines,
--json, and optionallyjq. - You need to move quickly through a build → timeline → logs → tests workflow without paying the context cost of loading many tools.
- You are working in a plain terminal, CI job, or one-off bash session where CLI output is easier than MCP round-trips.
Prefer MCP tools or the
ci-analysisskill when those tools are already loaded in context. The CLI is the context-efficient fallback.
Installation
Zero-install (requires .NET 10 SDK):
dnx lewing.helix.mcp <command>
Or install as a global tool:
dotnet tool install -g lewing.helix.mcp
Local repo fallback:
dotnet run --project src/HelixTool -- <command>
Examples in this skill use hlx; replace with the dnx or dotnet run form if needed.
Authentication
hlx supports anonymous access for public data and explicit auth for private Helix/AzDO.
- Helix: set
HELIX_ACCESS_TOKEN=...or runhlx login;hlx logoutremoves the stored token. - AzDO: resolution order is
AZDO_TOKEN→ Azure CLI /az login→az account get-access-token→ anonymous for public projects such asdnceng-public/public. - Useful checks:
hlx auth-status
hlx azdo auth-status --json
Progressive Discovery
hlx describe
hlx describe azdo search-log
hlx azdo search-log --schema
hlx azdo search-log --help
hlx describe— routing: which command handles what?hlx describe <command>— usage: parameters, defaults, and--schemahints.hlx <command> --schema— full JSON output shape (when you need exact nesting).<command> --help— all flags and arguments.hlx llms-txtstill exists for compact CLI notes, butdescribeis now the recommended discovery path for agents. There is nohlx ci-guideCLI command yet; usehelix_ci_guide(repo)/ci://profileswhen MCP is available.
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.
- 5d ago First seen · 123 lines · 113 tokens per session scan A 98295e53481c
helix-cli is a skill published in the GitHub repository lewing/helix.mcp (4 stars, last pushed today), licensed MIT. It adds 113 tokens to every session and 1,789 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
azdo-build-investigator
Investigate CI failures for dotnet/maui PRs and the nightly/official signed build — build errors, Helix test logs, and binlog analysis. Use when asked about failing checks, CI status, test failures, 'why is CI red', 'build failed', 'what's failing on PR', 'is this PR ready to merge', Helix failures, device test…
developer-security
Security best practices for gh-aw workflows and Go code: template injection prevention, shell script security, supply chain hardening, and static analysis integration.
ci-validation-gates
Defensive CI/CD patterns: semver validation, token checks, retry logic, draft detection — earned from v0.8.22.
github-script
Write robust JavaScript for GitHub Actions github-script steps.
github-workflows-query
List GitHub Actions workflows with perpage pagination support.
ci-fix
Common safety and triage protocol for .NET MAUI CI-fixer workflows. Use whenever investigating, creating, or advancing a [ci-fix] or [ci-fix-net11] pull request from a ci-scan issue, including frozen ownership snapshots, Continue/Watch/Stop/Skip classification, manual single-issue dispatches, and scheduled sweeps.