dshcode: Skill for Claude Code

.agents/skills/manps/SKILL.md

manps is a skill for Claude Code, Codex from whitelonng/dshcode. It costs 10 tokens per session (340 once invoked), scanned A, original, MIT.

A mancode project-health scan that checks areas such as dependencies, security, dead code, and configuration. It can also support an interactive remediation review when requested.

In plain words
What is it for?
Scanning project health, reviewing dependency or security issues, finding unused code, and checking configuration.
Why use it?
A repository can accumulate maintenance problems across several areas that are easy to miss in ordinary feature work. This gives those areas a focused check.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is whitelonng/dshcode's own configuration. It tells Claude Code and Codex how to work on dshcode itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything dshcode configures →

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/.agents/skills/manps/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/whitelonng/dshcode

Made for: Claude Code, Codex.

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.

agentmods badge for manps

README.md
[![agentmods](https://agentmods.dev/badge/skills/whitelonng/dshcode/manps/github.svg)](https://agentmods.dev/skills/whitelonng/dshcode/manps)
Your own site
<a href="https://agentmods.dev/skills/whitelonng/dshcode/manps"><img src="https://agentmods.dev/badge/skills/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.

agentmods 80×15 button for manps

Your own site · 80×15
<a href="https://agentmods.dev/skills/whitelonng/dshcode/manps"><img src="https://agentmods.dev/badge/skills/whitelonng/dshcode/manps.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 340 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00010 $0.00340
Opus 5.5 $0.00004 $0.00136
Sonnet 5.5 $0.00002 $0.00068
Haiku 4.5 $0.00001 $0.00034

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

Security

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.

.agents/skills/manps/SKILL.md · 27 lines

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.

  1. Reuse a mancode status --brief --json snapshot already obtained in this conversation. Only when none exists, run it once from the project root. Require an active, ready mancode Continuity runtime.
  2. Run the health action below directly. A local scan needs no TaskRef, actor identity, or explicit session.
  3. 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, or config).
  • Add --remediate only 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.

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.

  1. 1mo ago First seen · 27 lines · 10 tokens per session scan A 6056d615a4d3

Subscribe to this mod's changes

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

Related

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.

xlight/deepseek-visionary · 46 tokens

openspec-archive-change

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

creativedswork/dscode · 31 tokens

company-employee

The protocol every employee of a PenguinHarness organization follows — read the handbook first, act on [orgtrigger] work runs, schedule tickets from the desk session and do the work in ticket sessions, block instead of idling, ask the board in the all-hands channel before anything heavy, costly, irreversible or…

Prism-Shadow/penguin-harness · 85 tokens

company-ceo

Run a PenguinHarness organization as its CEO — turn the mission into a ticket tree, hire HR and finance first, partition the shared workspace, schedule the calendar, open a channel per stream, review tickets and report to the board in the all-hands channel.

Prism-Shadow/penguin-harness · 56 tokens

company-hr

Run HR for a PenguinHarness organization — guarantee every employee has an enabled calendar event, hire and offboard employees (channels included), evaluate and improve them (with the default-rsi-toolkit plugin's agent-optimization skill), and keep the handbook's role conventions current.

Prism-Shadow/penguin-harness · 58 tokens

company-mirror

Run a PenguinHarness organization that mirrors a real company — one digital twin per real colleague, each twin's desk bound to that colleague's chat bot, twins answering what the handbook already knows and relaying the rest to one another instead of hiring, scheduling and filing tickets.

Prism-Shadow/penguin-harness · 58 tokens