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/whitelonng/dshcode/manbagit 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/manba)<a href="https://agentmods.dev/commands/whitelonng/dshcode/manba"><img src="https://agentmods.dev/badge/commands/whitelonng/dshcode/manba.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.00010 | $0.00675 |
| Opus 5 | $0.00005 | $0.00338 |
| Sonnet 5 | $0.00002 | $0.00135 |
| Haiku 4.5 | $0.00001 | $0.00068 |
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 today.
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 — 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 --jsonsnapshot 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.actorIdis absent, ask for a display name and runmancode team identity create --name "<display name>". - Reuse
session.sessionIdwhen present. If status has no current session, reuse an explicit session ID already retained in this conversation. Only if neither exists, runmancode context session new --client cursorexactly once and retain the returned session ID. Use--client cursoron 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 cursorand finish withworkflow completeplus the typed--outcome.
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.
- today First seen · 31 lines · 10 tokens per session scan A 0393f53213e5
manba is a command published in the GitHub repository whitelonng/dshcode (711 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 675 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-09-03.
Other commands, from other repositories
delegate-review
Run OCR in delegation mode — OCR handles file selection and rules, the host agent performs the actual review.
commit
Please summarize your current changes, generate a commit message in English, then add and commit.
test
Complete test execution flow including backend and frontend tests, lint checks, and coverage reports.
harness
Run the full Auto-Harness orchestration flow. /auto-harness:harness.
qa-parallel
Advance parallel Evaluator-side actions only. Auto-selects review, QA, retest, or final report from status.md. /auto-harness:qa-parallel [sprint].
build-parallel
Advance parallel Generator-side actions only. Auto-selects contract, build, or fix from status.md. /auto-harness:build-parallel [sprint].