Borrowing it
Nothing to install: this file belongs to cyanseek/dsh-native-playbook. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/cyanseek/dsh-native-playbook/main/AGENTS.mdgit clone --depth 1 https://github.com/cyanseek/dsh-native-playbookWrote 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/instructions/cyanseek/dsh-native-playbook/agents-md)<a href="https://agentmods.dev/instructions/cyanseek/dsh-native-playbook/agents-md"><img src="https://agentmods.dev/badge/instructions/cyanseek/dsh-native-playbook/agents-md.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.1 | $0.00919 | $0.00919 |
| Opus 5 | $0.00460 | $0.00460 |
| Sonnet 5 | $0.00184 | $0.00184 |
| Haiku 4.5 | $0.00092 | $0.00092 |
Grade A, and why
dsh-native-playbook AGENTS.md 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository guidance
Goal
Map a user's task to the most appropriate native DeepSeek Harness capability before recommending an external plugin or custom workaround.
Non-goals
- Do not become a third-party plugin registry.
- Do not mirror all upstream documentation.
- Do not add plugin-only resolver logic; the runtime adapter must call the shared resolver.
- Do not collect telemetry.
Repository map
catalog/task-map.yml: curated task-to-capability mappings.generated/: deterministic facts generated from one official upstream commit.activation-recipes/: reviewed, version-gated, reversible native activation recipes.skills/dsh-native-playbook/: concise Skill plus focused references..codex-plugin/plugin.json: thin Codex skill-only plugin adapter overskills/.cordis.patch.yml: installable DSH bundle layer for the runtime adapter.src/: shared resolver, profile inspector, installer, CLI, API, and thin DSH adapter.scripts/: upstream sync and repository validation.tests/: behavior, profile, installer, and Skill contract tests.
Source-of-truth hierarchy
- Current official DeepSeek Harness source files pinned in
generated/upstream.json. - Effective profile output from
dsh --profile <name> --dump-config. - Curated intent and fallback policy in
catalog/task-map.yml. - Human-facing explanations in the Skill and READMEs.
Package existence alone is never evidence that a capability is ready.
Generated and curated files
- Never hand-edit
generated/upstream.jsonorgenerated/UPSTREAM_COMMIT. - Run
pnpm sync:upstreamto update generated facts. - Never let upstream sync rewrite
catalog/task-map.ymlor hand-authored recipes. - A task-map reference to a removed upstream tool must fail validation.
Commands
pnpm lint
pnpm typecheck
pnpm test
pnpm build
pnpm validate:skill
pnpm validate:plugin
pnpm validate:dsh-plugin
pnpm verify:upstream
pnpm smoke:json
pnpm smoke:consumer
pnpm metrics
Run the complete set before release. Use pnpm sync:upstream -- --source-dir <checkout>
when validating against a trusted local upstream checkout.
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.
- 7d ago First seen · 98 lines · 919 tokens per session scan A 8a0a715f5d22
dsh-native-playbook AGENTS.md is an instructions file published in the GitHub repository cyanseek/dsh-native-playbook (5 stars, last pushed 23d ago), licensed MIT. It adds 919 tokens to every session, about $0.0046 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-08-31.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.