Borrowing it
Nothing to install: this file belongs to whitelonng/dshcode. 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/whitelonng/dshcode/master/.cursor/commands/manps.mdgit clone --depth 1 https://github.com/whitelonng/dshcodeWrote 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/commands/whitelonng/dshcode/manps)<a href="https://agentmods.dev/commands/whitelonng/dshcode/manps"><img src="https://agentmods.dev/badge/commands/whitelonng/dshcode/manps/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/commands/whitelonng/dshcode/manps"><img src="https://agentmods.dev/badge/commands/whitelonng/dshcode/manps.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.00007 | $0.00335 |
| Opus 5.5 | $0.00003 | $0.00134 |
| Sonnet 5.5 | $0.00001 | $0.00067 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
manps 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 1mo 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
mancode mode: manps
Purpose: scan project health and review bounded remediation.
Enter through mancode
Before the first command, use ./node_modules/.bin/mancode when it exists, otherwise mancode; check that selected binary with --version once and never mix binaries or versions. In every command below, replace the literal mancode with that selected binary path when the local binary exists.
- Reuse a
mancode status --brief --jsonsnapshot already obtained in this conversation. Only when none exists, run it once from the project root. Require an active, ready mancode Continuity runtime. - Run the health action below directly. A local scan needs no TaskRef, actor identity, or explicit session.
- Never read or write legacy mode authority before or after the scan.
Mode action
- Run
mancode manps [area]through the same public command entry (all,deps,security,dead-code, orconfig). - Add
--remediateonly when the operator explicitly requests an interactive remediation review.
Treat the compact status as the public mancode Continuity runtime view. In operator-facing narration, say mancode or mancode Continuity; never prefix this mode or its actions with a version label.
The local scan and an explicitly requested remediation do not require a TaskRef, workflow revision, actor, or session. Never turn their report files into workflow authority.
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.
- 1mo ago First seen · 26 lines · 7 tokens per session scan A 917dd5d10426
manps is a command published in the GitHub repository whitelonng/dshcode (704 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 335 once invoked, about $0.0000 per session on Opus 5.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-09-03.
Other commands, from other repositories
root-cause
Use when any test fails, bug appears, or behaviour surprises you, before proposing a fix - find the cause and prove it, by reading real evidence, tracing bad values back to their origin, comparing against a working case, and testing one hypothesis at a time.
trace-regression
Investigate a newly introduced bug or regression to identify the offending change and formulate a fix.
flutter-build
Fix Dart analyzer errors and Flutter build failures incrementally. Invokes the dart-build-resolver agent for minimal, surgical fixes.
fix-issue
Command "fix-issue" from HKTITAN/cursor-best-practices, covering steps and rules.
speckit.review.errors
Error handling review — silent failure detection, catch block analysis, error logging.
checklist
Generate a custom checklist for the current feature based on user requirements.