Apache ShardingSphere is a database enhancement layer that makes heterogeneous databases easier to access and govern as a unified system, without replacing the underlying databases. It supports distributed database capabilities such as sharding, read-write splitting, SQL federation, encryption, masking, auditing, and traffic control for enterprise data architectures.
Borrowing it
Nothing to install: this file belongs to apache/shardingsphere. 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/apache/shardingsphere/master/AGENTS.mdgit clone --depth 1 https://github.com/apache/shardingsphereWrote 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/apache/shardingsphere/agents-md)<a href="https://agentmods.dev/instructions/apache/shardingsphere/agents-md"><img src="https://agentmods.dev/badge/instructions/apache/shardingsphere/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/apache/shardingsphere/agents-md"><img src="https://agentmods.dev/badge/instructions/apache/shardingsphere/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.02514 | $0.02514 |
| Opus 5.5 | $0.01006 | $0.01006 |
| Sonnet 5.5 | $0.00503 | $0.00503 |
| Haiku 4.5 | $0.00251 | $0.00251 |
Grade A, and why
shardingsphere 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ShardingSphere Codex Development Guide
Follow this guide; paths are repository-relative.
Instruction Sources and Routing
- Inspect the applicable
CODE_OF_CONDUCT.mdsection before changing code or tests. - Before Maven, E2E, Proxy startup, database clients, IDE/MCP runs, large structured analysis, or commands likely to exceed 100 lines, read or reuse
.codex/context/token-efficiency.mdand follow its Command Contract. Read.codex/context/docker-resources.mdbefore direct or indirect Docker use. - Before changing production, tests, scripts, build logic, generated source, or behavior configuration, read
.codex/skills/code-implementation/SKILL.mdthrough EOF. Read-only and prose-only work does not activate it, and no Skill grants authority or scope. - If Skill discovery omits required
code-implementation, load its repository file directly. A missing required canonical source keeps ordinary writes read-only; only an exact user-authorized policy or harness repair may use.codex/harness/agents/policy-maintenance.md. - For read-only code or test analysis, planning, design, or review, read the implementation rules without activating the write workflow. Load testing, removal, contract, or non-regression rules only when that topic can affect the requested conclusion.
- Before classifying an artifact as unused or removable, read and apply the complete removal and contract-impact rules.
- For runtime diagnosis, read
.codex/context/runtime-triage.md; an authorized fix activatescode-implementationbefore its first write. - Select optional Skills from their catalog triggers. Read
.codex/context/cross-cutting-skills.mdonly when a matching trigger may apply, and use the smallest matching Skill set. - Before running or assessing a repository verification command, read the verification rules. For an authorized change, read
.codex/context/change-completion.mdbefore completion review or handoff. - Before revising documentation, Skills, prompts, comments, or configuration prose, read
.codex/context/documentation-wording.md. - Keep task-specific notes outside repository Skills.
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 Changed · +1 lines · +18 tokens per session 2d8f483f8563
- 15d ago Changed · +4 lines · -18 tokens per session ea691616354c
- 17d ago Changed · +76 tokens per session c44f4c6652be
- 18d ago Changed · -6 lines · -99 tokens per session 54268003dd87
- 1mo ago Changed · +41 lines · +661 tokens per session 6036f2f7cb0a
- 1mo ago Changed · -33 lines · -1,081 tokens per session 1d429a52f864
- 1mo ago Changed · -63 lines · -2,007 tokens per session bd3df23fd6bf
- 1mo ago First seen · 188 lines · 4,964 tokens per session scan A 3fc070510d38
shardingsphere AGENTS.md is an instructions file published in the GitHub repository apache/shardingsphere (20,817 stars, last pushed today), licensed Apache-2.0. It adds 2,514 tokens to every session, about $0.0101 per session on Opus 5.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-09-03.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.