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/zhigege666/lingshu-gate/agents-mdgit clone --depth 1 https://github.com/zhigege666/Lingshu-GateWrote 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/zhigege666/lingshu-gate/agents-md)<a href="https://agentmods.dev/instructions/zhigege666/lingshu-gate/agents-md"><img src="https://agentmods.dev/badge/instructions/zhigege666/lingshu-gate/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.00606 | $0.00606 |
| Opus 5 | $0.00303 | $0.00303 |
| Sonnet 5 | $0.00121 | $0.00121 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
Lingshu-Gate 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 3d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository instructions
These instructions apply to the entire repository.
Product identity and scope
- Use
Lingshu Gatefor the product,Gatefor short prose,lingshu_gatefor the Python package,lingshu-gatefor commands and artifacts,LINGSHU_GATE_for environment variables, andgate_for first-party MCP tools. - Use
MCPonly for the open protocol and its generic messages, transports, servers, tools, resources, and prompts. - Keep downstream connections vendor-neutral through the generic manifest and protocol transports. Use neutral examples and original project text.
- The only repository-owned Skill is
.agents/skills/lingshu-gate-upload-build-start/. It is part of the Project Delivery boundary and must retain confirmation, digest, idempotency, credential, and classification checks.
Architecture boundaries
- Keep protocol transport, application policy, persistence, and HTTP presentation separable.
- Control-plane writes require explicit permission checks and auditable events.
- Tool discovery never grants access. Classification review and publication remain distinct operations.
- Credentials are stored outside manifests, encrypted at rest, masked in responses, and never logged as values.
- Project upload, build, deployment, overwrite, startup, cancellation, and abandonment keep independent confirmation boundaries.
- Docker Core remains unprivileged, read-only at the root filesystem, and disconnected from container-engine sockets.
- SQLite deployment is single-writer and single-Core unless a different store is implemented and tested.
Change discipline
- Read the nearest code, tests, and documentation before editing.
- Preserve unrelated work in a dirty worktree.
- Prefer focused changes with tests for observable behavior.
- Failure paths must fail closed and return structured, actionable errors without secrets.
- Do not add silent fallback aliases for renamed package, environment, event, database, cookie, or tool identities.
- Use neutral commit and release text that describes the engineering result.
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.
- 3d ago First seen · 57 lines · 606 tokens per session scan A a1559c73f980
Lingshu-Gate AGENTS.md is an instructions file published in the GitHub repository zhigege666/Lingshu-Gate (0 stars, last pushed 2d ago), licensed Apache-2.0. It adds 606 tokens to every session, about $0.0030 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
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).
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.