A mancode workflow for reproducing, diagnosing, fixing, and verifying a bug or regression, meaning a change that makes previously working behavior fail.

Handling bug reports, reproducing failures, identifying their cause, implementing a correction, and verifying the result.

It structures debugging so the reported failure is investigated and the fix is checked against the original problem.

How whitelonng/dshcode configures Claude Code and Cursor

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/whitelonng/dshcode/master/.cursor/commands/manba.md

Clone the repo

git clone --depth 1 https://github.com/whitelonng/dshcode

Made for: Claude Code, Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/whitelonng/dshcode/manba/github.svg)](https://agentmods.dev/commands/whitelonng/dshcode/manba)

Your own site

<a href="https://agentmods.dev/commands/whitelonng/dshcode/manba"><img src="https://agentmods.dev/badge/commands/whitelonng/dshcode/manba/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/whitelonng/dshcode/manba"><img src="https://agentmods.dev/badge/commands/whitelonng/dshcode/manba.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 675 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00010	$0.00675
Opus 5.5	$0.00004	$0.00270
Sonnet 5.5	$0.00002	$0.00135
Haiku 4.5	$0.00001	$0.00068

Measured 1mo ago against content hash 0393f53213e5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

manba 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.

.cursor/commands/manba.md · 31 lines

How it starts

The opening of the file, as written. The whole thing — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.

mancode mode: manba

Purpose: reproduce, diagnose, fix, and verify a regression.

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 --json snapshot already obtained in this conversation. Only when none exists, run it once from the project root. Never read or write the legacy authority file.
If identity.actorId is absent, ask for a display name and run mancode team identity create --name "<display name>".
Reuse session.sessionId when present. If status has no current session, reuse an explicit session ID already retained in this conversation. Only if neither exists, run mancode context session new --client cursor exactly once and retain the returned session ID. Use --client cursor on every command that uses this session.
Reuse the current TaskRef. To bind a supplied existing task, run mancode context resume <namespace:ULID> --session <id> --client cursor.
For an existing task, read only the needed Context Pack with mancode context show --purpose implement --session <id> --client cursor; include --task <namespace:ULID> when it is not yet bound. For a new task, create it through the mode action first, then read the returned TaskRef's Context Pack.

Mode action

For a new diagnostic task, run mancode workflow create manba "<task>" --session <id> --client cursor.
Before changing code, establish the expected behavior from reproducible evidence, tests, documentation, history, or the current semantic owner. If the bug goal is clear but the correct behavior cannot be established, ask one focused question and wait instead of inventing product behavior.
If the requested fix conflicts with repository evidence or crosses a hard-risk boundary, show the conflict and obtain a focused confirmation or route the decision through /man; do not treat an explicit but unsound fix instruction as sufficient evidence.
When this is a child investigation, add --parent <namespace:ULID>; report and merge the typed outcome through the mancode child commands.
Change lifecycle only with mancode workflow update <namespace:ULID> --status <status> --expected-revision <n> --session <id> --client cursor and finish with workflow complete plus the typed --outcome.

Read the full file on GitHub · 31 lines

Changes

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 · 31 lines · 10 tokens per session scan A 0393f53213e5

Subscribe to this mod's changes

manba is a command published in the GitHub repository whitelonng/dshcode (704 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 675 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.

Debugging agent deepseek deepseekharness-plugin dsh-plugin harness

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.

hamr0/liteagents · 52 tokens

dshcode: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

mancode mode: manba

Enter through mancode

Mode action

What this file has done since we first saw it

Other commands, from other repositories

root-cause

trace-regression

flutter-build

fix-issue

speckit.review.errors

checklist