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 instructions/oomol-lab/dsh-oomol/agents-mdgit clone --depth 1 https://github.com/oomol-lab/dsh-oomolWrote 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/oomol-lab/dsh-oomol/agents-md)<a href="https://agentmods.dev/instructions/oomol-lab/dsh-oomol/agents-md"><img src="https://agentmods.dev/badge/instructions/oomol-lab/dsh-oomol/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 | $0.00153 | $0.00153 |
| Opus 5 | $0.00077 | $0.00077 |
| Sonnet 5 | $0.00031 | $0.00031 |
| Haiku 4.5 | $0.00015 | $0.00015 |
Grade A, and why
dsh-oomol 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 4d 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.
What it actually says
Development guidelines
- Keep the plugin thin: use OOMOL MCP for Connector discovery and execution.
- Keep Provider credentials in OOMOL Connector; never persist them in this repository or a Cordis patch.
- Resolve the OOMOL MCP key through the Harness credentials service first, then the launching environment.
- Do not read OOCLI internal auth files. Add a stable OOCLI integration contract if bootstrap needs one.
- Preserve progressive discovery; do not register every Connector Action as a permanent Harness tool.
- Treat DeepSeek Harness as a fast-moving developer preview dependency and test upgrades explicitly.
- Use
import typefor type-only imports and retain NodeNext.jssuffixes for local module imports. - Run
pnpm checkbefore delivery.
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.
- 4d ago First seen · 11 lines · 153 tokens per session scan A eb538f8ffa06
dsh-oomol AGENTS.md is an instructions file published in the GitHub repository oomol-lab/dsh-oomol (13 stars, last pushed 14d ago), licensed MIT. It adds 153 tokens to every session, about $0.0008 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-30.
Other instructions, from other repositories
OpenQuantum AGENTS.md
AGENTS.md instructions for xi-zhao/OpenQuantum, covering openquantum, 四个职责面, 扩展对象不可混用, 不变量 and 代码位置.
dsh-TUI AGENTS.md
AGENTS.md instructions for ccch1mneyyy/dsh-TUI, covering agents.md, 仓库布局, 命令, 上游边界与契约 and 约定与红线.
DSH-better-sidebar AGENTS.md
AGENTS.md instructions for omdsh-dev/DSH-better-sidebar, covering dsh-better-sidebar 仓库规则（agents）, 1. 仓库硬约束（必须遵守）, 2. ci 挂载冒烟（plugin-mount job / pnpm test:mount）, 3. dsh 0.1.2 适配要点（0.1.2-rc.1+ 基线） and 4. npm 发版（github release → npm publish）.
sandbase-harness AGENTS.md
AGENTS.md instructions for sandbaseai/sandbase-harness, covering sandbase harness agent instructions, project identity, repository map, role a: project maintenance and issue workflow.
dsh-worktable AGENTS.md
Instructions for Aisland-SJL/dsh-worktable, covering dsh-worktable 项目规则, 协作方式（用户定案，最高优先级）, 边界, 构建与验证 and 领域约定（会话中必须遵守）.
modsearch AGENTS.md
AGENTS.md instructions for liustack/modsearch, covering project overview (for ai agent), goal, technical approach, code organization and skills directory.