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-site-syncgit 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-site-sync)<a href="https://agentmods.dev/skills/ethanyoq/skill-hub/dsh-doc-site-sync"><img src="https://agentmods.dev/badge/skills/ethanyoq/skill-hub/dsh-doc-site-sync/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-site-sync"><img src="https://agentmods.dev/badge/skills/ethanyoq/skill-hub/dsh-doc-site-sync.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.00067 | $0.01413 |
| Opus 5.5 | $0.00027 | $0.00565 |
| Sonnet 5.5 | $0.00013 | $0.00283 |
| Haiku 4.5 | $0.00007 | $0.00141 |
Grade A, and why
dsh-doc-site-sync 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-site-sync — 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Synchronizing the DeepSeek Harness Documentation Site
Keep repository Markdown as the only editable content source. Treat the website as a tested projection: website/docs.ts selects public pages, scripts/project-doc-site.ts rewrites them into the disposable website/.generated/ tree, and VitePress builds that tree.
Repository translations follow the sibling pairing contract: English foo.md, Chinese foo.zh.md, and foo.i18n.yaml live together. Never create zh-CN/ or other locale directories for website content. The site route trees are independent of that source layout: foo.zh.md projects to the root route and foo.md projects to the matching /en/ route.
Read the owning contracts
- Read docs/AGENTS.md and use dsh-doc-standards when deciding where content belongs or changing product documentation prose.
- For an edited bilingual source, follow the lightweight routine path in docs/AGENTS.md and the pairing contract; never invoke the extended translation skill automatically.
- Read the current
DocsPagetype and entries in website/docs.ts before changing the manifest; do not rely on a remembered field set. - Read website/.vitepress/config.ts before adding a new section, sidebar collection, locale, or top-level navigation item.
Classify the change
- Edit an already published page: change only its canonical Markdown source. Do not touch the manifest unless its route or navigation metadata changes.
- Publish a new page: create it in its owning
docs/tier, then add one manifest entry. - Rename, move, or remove a page: update the canonical file, manifest entry, and inbound repository links atomically. Remove stale manifest entries;
docs:checkrejects missing sources. - Publish a generated catalog: map the generated
docs/file, but change its generator or source metadata rather than editing the catalog by hand. - Change site structure: update the manifest for ordinary pages; update VitePress configuration only when the existing sidebar, section, or locale model cannot express the change.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 87 lines · 67 tokens per session scan A d2fa857efa06
dsh-doc-site-sync is a skill published in the GitHub repository EthanYoQ/Skill-hub (11 stars, last pushed 8d ago), licensed MIT. It adds 67 tokens to every session and 1,413 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-site-sync, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
pr-watch
Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.
ho-apply-script
A skill for building a shell script that a person can safely use to apply a prepared patch. The script includes checks and apply, verify, and rollback modes, but does not commit or push changes.
devops-commander
Activates the DevOps-Commander agent for infrastructure, CI/CD, and cloud operations. Use when you need GitHub Actions or GitLab CI pipeline design, Dockerfile and docker-compose configuration, Kubernetes deployment manifests, Terraform/Pulumi infrastructure as code, Prometheus + Grafana monitoring setup, or incident…
ci-cd-builder
Create CI/CD pipelines — GitHub Actions, GitLab CI, Jenkins, and CircleCI with test, build, and deploy stages.
github-actions
Build GitHub Actions workflows — CI, CD, automated releases, dependency updates, and custom composite actions.
gitlab-ci
Create GitLab CI/CD pipelines — stages, jobs, caching, artifacts, environments, and Auto DevOps customization.