Borrowing it
Nothing to install: this file belongs to imsai-sh/dsh-1024store. 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/dsh-1024store/main/AGENTS.mdgit clone --depth 1 https://github.com/imsai-sh/dsh-1024storeWrote 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/dsh-1024store/agents-md)<a href="https://agentmods.dev/instructions/imsai-sh/dsh-1024store/agents-md"><img src="https://agentmods.dev/badge/instructions/imsai-sh/dsh-1024store/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.03301 | $0.03301 |
| Opus 5 | $0.01650 | $0.01650 |
| Sonnet 5 | $0.00660 | $0.00660 |
| Haiku 4.5 | $0.00330 | $0.00330 |
Grade A, and why
dsh-1024store 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository instructions
Public URL stability
- Canonical public paths:
/(rankings),/plugins(catalog),/plugins/:owner/:name(plugin detail),/docs/api(public API reference),/community(community feed),/community/p/:id(post),/community/about(rules),/accountand/community/u/:login(noindex). - Plugin API routes use the
/api/v1/prefix with plural resources (/api/v1/plugins,/api/v1/plugins/:owner/:name). The outward-facing search API ishttps://api.deepseek1024.com/v1/plugins/search. /plugin,/plugin/:owner/:name,/packages,/packages/:owner/:nameand/rankingsare permanent 301 sources only. Do not cite them as live URLs.- Treat public route paths as permanent SEO contracts. Do not rename or remove them without explicit user approval and a migration plan covering permanent redirects, canonical URLs, and existing inbound links.
- Page titles, descriptions, JSON-LD and the crawlable pre-hydration shell all come from
web/worker/seo-templates.tsandweb/worker/seo-content.ts. Both the Worker and the React app import them; never fork the copy into a page component or a translation file. - When replacing an already-published route, keep a permanent redirect from the old path to the canonical path.
API backward compatibility
- Every API is a published compatibility contract, whether it is currently used by the site, a non-Web client, a third party, an authenticated tool, an internal sync job or a WebSocket client. Never assume a site-only caller updates in lockstep with the Worker.
- Within an existing API version, do not remove or rename fields, change types or nullability, reinterpret values, change defaults, status/error codes, pagination, ordering, authentication behavior or important headers. Treat new response enum values as potentially breaking. Compatible additions must remain optional or ignorable to old clients.
- Breaking changes require a new versioned route while the previous route and its behavior remain available through an explicit migration and deprecation period.
web/contracts/api-surface.jsonis the exhaustive API inventory. Every Hono API route, Worker-owned API transport and public-host alias must be registered there. Versioned response schemas and golden semantic fixtures live beside it.- Run
npm run test:api-contractfor every API-related change. Do not make a failure green by casually rewriting a historical schema or golden fixture; contract changes require explicit API-owner review. Keep the route coverage test, historical request behavior and known consumer-adapter tests current.
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 · 171 lines · 3,301 tokens per session scan A a372941057b1
dsh-1024store AGENTS.md is an instructions file published in the GitHub repository imsai-sh/dsh-1024store (10 stars, last pushed 11d ago), licensed MIT. It adds 3,301 tokens to every session, about $0.0165 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.