Borrowing it
Nothing to install: this file belongs to imsai-sh/awesome-deepseek-harness-plugins. 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/imsai-sh/awesome-deepseek-harness-plugins/main/AGENTS.mdgit clone --depth 1 https://github.com/imsai-sh/awesome-deepseek-harness-pluginsWrote 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/imsai-sh/awesome-deepseek-harness-plugins/agents-md)<a href="https://agentmods.dev/instructions/imsai-sh/awesome-deepseek-harness-plugins/agents-md"><img src="https://agentmods.dev/badge/instructions/imsai-sh/awesome-deepseek-harness-plugins/agents-md/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/instructions/imsai-sh/awesome-deepseek-harness-plugins/agents-md"><img src="https://agentmods.dev/badge/instructions/imsai-sh/awesome-deepseek-harness-plugins/agents-md.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.01057 | $0.01057 |
| Opus 5 | $0.00528 | $0.00528 |
| Sonnet 5 | $0.00211 | $0.00211 |
| Haiku 4.5 | $0.00106 | $0.00106 |
Grade A, and why
awesome-deepseek-harness-plugins 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 9d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository instructions
This repository is the plugin catalog: the awesome list (catalog/plugins/*.json),
the plugin submission review/merge workflow, and the generated README directories. The
DSH 1024Store application — the deepseek1024.com site, its Worker, and the dsh1024 npm
package — lives in imsai-sh/dsh-1024store.
The submission gate is the product
- The public PR gate accepts changes to
catalog/plugins/*.jsononly; everything else is maintainer-bypass territory.scripts/review-plugin-submission.mjsis the trusted reviewer: it always runs from the base branch and treats the submitted checkout as data. - The
allow-unsafe-pr-checkout: trueflag in.github/workflows/plugin-review.ymlmust never be removed — without it every fork PR fails silently with no comment. - Verdicts are three-state: exactly one new entry on a non-draft PR auto-merges; updates/removals go green but wait for a maintainer; anything else fails with a comment. A failed review never closes the PR.
skills/submit-dsh-plugin/must stay in lockstep with the live submission spec: any change to CONTRIBUTING.md, the schema or categories, the PR template, the review workflow or scripts, or the merge flow updates the skill, its references, scripts, tests, and README install instructions in the same change.
Generated files
README.mdandcatalog/README.mdare bot-generated byscripts/build-readme.mjs. Never hand-edit them; change the generator and runnpm run readme:build. The catalog-sync workflow regenerates and force-pushes them via theCATALOG_DEPLOY_KEYdeploy key, which is also the documented branch-protection bypass.- The README hero screenshot lives on the orphan
assetsbranch of THIS repository, force-pushed by the catalog-sync workflow. Do not repoint it elsewhere. - The WeChat group QR image is
docs/assets/wechat-group.jpgin this repository (the site serves its own copy from the other repo).
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.
- 9d ago First seen · 68 lines · 1,057 tokens per session scan A 710040ee9bf0
awesome-deepseek-harness-plugins AGENTS.md is an instructions file published in the GitHub repository imsai-sh/awesome-deepseek-harness-plugins (225 stars, last pushed today), licensed MIT. It adds 1,057 tokens to every session, about $0.0053 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
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.
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).
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).
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.
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.