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 skills add EthanYoQ/Skill-hub --skill dsh-doc-standardsgit clone --depth 1 https://github.com/EthanYoQ/Skill-hubWrote 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/ethanyoq/skill-hub/dsh-doc-standards)<a href="https://agentmods.dev/skills/ethanyoq/skill-hub/dsh-doc-standards"><img src="https://agentmods.dev/badge/skills/ethanyoq/skill-hub/dsh-doc-standards/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/skills/ethanyoq/skill-hub/dsh-doc-standards"><img src="https://agentmods.dev/badge/skills/ethanyoq/skill-hub/dsh-doc-standards.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.00084 | $0.01436 |
| Opus 5.5 | $0.00034 | $0.00574 |
| Sonnet 5.5 | $0.00017 | $0.00287 |
| Haiku 4.5 | $0.00008 | $0.00144 |
Grade A, and why
dsh-doc-standards 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.
This is a copy
100% identical to dsh-doc-standards — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Applying the DeepSeek Harness Documentation Standard
The documentation rules live in docs/AGENTS.md. This workflow covers placement, corpus audits, budgets, and validation across Markdown, JSDoc, and code comments. It is guidance, not a script; use dsh-prose-standard for required coverage and editorial judgment, and never treat length alone as a defect.
Sources of truth (read, don't re-summarize)
- docs/AGENTS.md — hierarchy, tutorial/reference forms, taxonomy, budgets, and slop checklist.
- .agents/notes/README.md — when a decision earns an Agent Note, how to file it, and what goes inside one (the header block, per-lifecycle skeleton, and Alternatives-considered mandate, gated by
verify-agent-note-format); docs/postmortem/README.md — when an incident earns a postmortem. - docs/i18n/README.md — the bilingual pairing rules; editing either side of a pair obligates the counterpart in the same change.
- Root AGENTS.md — the standing orders whose budget discipline this skill protects.
- Archived Agent Notes — frozen historical snapshots excluded from editorial maintenance and evolving documentation gates.
Review structure before prose
Apply the standard's authoring order to every human-facing document in scope. Do not apply this structural pass to Agent Notes. Classify a postmortem as a reference scoped to one incident; preserve its required chronological evidence without treating chronology as a teaching sequence.
- Locate the document in the repository and navigation trees. State its own subject and identify its direct children.
- Set the permitted level of detail. Keep full detail about the document's subject, summarize direct children by purpose, responsibility, and high-level behavior, and move deeper explanations to their owning descendants with links. Treat test infrastructure as descendant-owned unless it is the document's subject.
- Classify the document from its intended use, not its path or title. A tutorial must lead through ordered work to an observable outcome; a reference must support lookup within an explicit scope without requiring sequential reading.
- For a tutorial, privately classify the starting reader and concepts as beginner, intermediate, or advanced. Trace each concept to its prerequisites, reorder premature material, and move optional advanced detail to a later tutorial or reference.
- Split substantial mixed forms. Put a small secondary form in a clearly labeled section.
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 · 57 lines · 84 tokens per session scan A 8a648b26f28a
dsh-doc-standards is a skill published in the GitHub repository EthanYoQ/Skill-hub (11 stars, last pushed 8d ago), licensed MIT. It adds 84 tokens to every session and 1,436 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to dsh-doc-standards, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
wiki
Markdown-first knowledge base where the LLM acts as librarian. Ingests raw sources, compiles and interlinks topic files, self-maintains an index. No vector DB or embeddings required -- uses LLM-native navigation over structured markdown up to 400K words.
debrief
This skill should be used when the user asks to "debrief", "record what happened", "session summary", "write a debrief", or wants to capture session activity (commits, task state changes, decisions, issues) into a structured record for the next session.
document-processor
Activates DocumentProcessor for intelligent processing of Word, PDF, PowerPoint, and Excel files. Use when you need to extract, summarize, redline, or transform documents in any Office format — compare versions, extract tables, generate document outlines, convert formats, or produce structured data from unstructured…
create-proposal
Create a PandaDoc proposal for a client.
contract-generator
Draft professional legal contracts — NDAs, service agreements, employment contracts, and SaaS terms with customizable clauses.
docx
Create, read, edit, and manipulate Word .docx files with full formatting — tables of contents, headings, page numbers, letterheads, tracked changes.