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 commands/manderse21/claude-powershell-lsp/statusgit clone --depth 1 https://github.com/manderse21/claude-powershell-lspWhat 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.00023 | $0.00302 |
| Opus 5 | $0.00012 | $0.00151 |
| Sonnet 5 | $0.00005 | $0.00060 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
status 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 2d 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.
What it actually says
Show the compact powershell-lsp health status.
This is the same preflight doctor as /powershell-lsp:doctor, rendered short: one line per check
plus the summary, with the per-check detail and remediation omitted. It runs the identical checks
and produces the identical statuses and exit code -- only the presentation differs. Like the
doctor, it is report-only and changes nothing.
pwsh -NoLogo -NoProfile -File "$env:CLAUDE_PLUGIN_ROOT/scripts/doctor.ps1" -Summary
The first line is followed by a version: header naming the installed plugin build. It always
renders, it is not one of the checks, and it is the line to keep when the output is pasted into a
bug report.
Report the output as-is -- it is already a summary, so do not summarize it further. Add at most one sentence of interpretation:
- All PASS -- say the plugin is healthy.
- Any UNKNOWN and no FAIL -- say it is healthy as far as it could tell, and name what it could not determine. UNKNOWN is never a failure.
- Any FAIL -- name the failing check and point the user at
/powershell-lsp:doctorfor that check's detail and its specific fix.
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.
- 2d ago First seen · 29 lines · 23 tokens per session scan A 1ddab8064d5e
status is a command published in the GitHub repository manderse21/claude-powershell-lsp (6 stars, last pushed 8d ago), licensed Apache-2.0. It adds 23 tokens to every session and 302 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 commands, from other repositories
commands
Lint and validate command definition files.
meta-errors
Analyze error patterns and prevention recommendations.
commands-deprecated-directory
Commands directory is deprecated, migrate to Skills.
dumpstack
Helps examine thread call stacks. While clrstack is more commonly used for managed call stacks, dumpstack can also be used to inspect stack frames, including native ones.
printexception
Prints information about an exception object.
dumpmt
Displays details about method tables (MethodTable).