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/whitelonng/dshcode/mannpx skills add whitelonng/dshcode --skill mangit 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/skills/whitelonng/dshcode/man)<a href="https://agentmods.dev/skills/whitelonng/dshcode/man"><img src="https://agentmods.dev/badge/skills/whitelonng/dshcode/man.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.00011 | $0.02353 |
| Opus 5 | $0.00005 | $0.01177 |
| Sonnet 5 | $0.00002 | $0.00471 |
| Haiku 4.5 | $0.00001 | $0.00235 |
Grade A, and why
man 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 yesterday.
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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mancode mode: man
Purpose: clarify, plan, implement, verify, and review governed work.
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 the request is only a read-only project orientation, introduction, explanation, or summary, inspect the repository and answer directly without creating an actor, session, TaskRef, or workflow. Do not turn an orientation request into a
plan_onlyworkflow. - Only for requested governed task work, 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 codexin Codex,mancode context session new --client zcodein ZCode, ormancode context session new --client kimi-codein Kimi Code exactly once, then retain the returned session ID. Use--client codexin Codex,--client zcodein ZCode, or--client kimi-codein Kimi Code 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 <active-client>. - For an existing task, read only the needed Context Pack with
mancode context show --purpose plan --session <id> --client <active-client>; 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.
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.
- yesterday First seen · 53 lines · 11 tokens per session scan A be5912bd81d0
man is a skill published in the GitHub repository whitelonng/dshcode (711 stars, last pushed yesterday), licensed MIT. It adds 11 tokens to every session and 2,353 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 skills, from other repositories
visionary-cli
Analyze images with DeepSeek's vision model via the visionary-server CLI. Use this whenever the user provides an image, photo, screenshot, or document with images - run vision to look at it rather than guessing.
deepseek-harness
Use when building AI agent applications with a plugin-based architecture — Web UI, CLI, Python SDK, Cordis plugin system, multi-model orchestration. DeepSeek Harness (dsh): open-source agent harness by DeepSeek AI where everything is a plugin, powered by Cordis for spatiotemporal composability.
deepseek-harness
Use this skill whenever the user wants to call DeepSeek V4-Pro / V4-Flash (or its legacy aliases deepseek-chat / deepseek-reasoner), or you see code that imports from openai import OpenAI with baseurl="https://api.deepseek.com". This skill teaches you the 10 protocol contract rules required to avoid the 16 documented…
web-ui-motion
Build polished front-end UI together with a signature motion effect in a single self-contained HTML file, combining SVG.js / SVG filters and the Canvas 2D API. Use when the user asks to build a web page, landing page, dashboard, or component that has a special visual effect, animation, particle system, fluid/water…
openspec-propose
Create a complete OpenSpec proposal with design, specs, prototype, and tasks. Use when the user wants a change ready for implementation.
prototype-workflow
Generate and lifecycle-manage HTML prototypes for UI exploration and OpenSpec changes. Use when creating, validating, completing, or archiving a UI prototype.