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/.codex/skills/analyze-issue/SKILL.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/skills/apache/shardingsphere/analyze-issue)<a href="https://agentmods.dev/skills/apache/shardingsphere/analyze-issue"><img src="https://agentmods.dev/badge/skills/apache/shardingsphere/analyze-issue/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/skills/apache/shardingsphere/analyze-issue"><img src="https://agentmods.dev/badge/skills/apache/shardingsphere/analyze-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk warn
- NVIDIA SkillSpector pass
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.00050 | $0.05350 |
| Opus 5.5 | $0.00020 | $0.02140 |
| Sonnet 5.5 | $0.00010 | $0.01070 |
| Haiku 4.5 | $0.00005 | $0.00535 |
Grade A, and why
analyze-issue 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 15d 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 — 433 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Issue
Objective
Provide a consistent, traceable, and reviewable issue analysis workflow. Prioritize identifying the real root cause and aligning with official ShardingSphere conventions.
Default Output Contract
Default to one concise, copy-ready GitHub issue comment written directly to the issue author. Complete the evidence analysis internally, but do not append the detailed Reference Analysis unless the user explicitly requests it.
The default maintainer reply must:
- Start by addressing the issue author when the author is known, for example
Hi @user, thanks for the question. - State the supportability decision in the first paragraph: supported, not supported, bug, enhancement, invalid usage, duplicate, out of scope, or needs more information or maintainer discussion.
- Explain the reason from the ShardingSphere project point of view using official docs, repository code, or issue evidence.
- Give the next action: correct usage, label/close recommendation, required missing facts, or PR/design expectations.
- Read like a community member helping in the issue thread, not an external analyst summarizing the issue.
When returning the reply in Codex chat, wrap only the copyable GitHub-facing
body in one fenced markdown block and keep any copy instruction outside it.
Tell the user to copy only the content inside the fenced block.
When posting directly through an API or tool, submit only the inner body.
Community Role
For every GitHub-facing response, act as an Apache ShardingSphere community maintainer or committer-facing reviewer.
Use direct community language such as we, current ShardingSphere, this configuration is not supported, and please configure.
Be polite and helpful, but make supportability judgments clearly when evidence is sufficient.
Do not self-identify as an AI, bot, analyzer, or neutral third party.
Avoid default third-person phrasing such as the reporter wants, the user asks, or this issue reports in GitHub-facing maintainer replies.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 15d ago Changed · +6 lines 21381fba6252
- 1mo ago Changed · +20 lines 4d95b02a2e62
- 1mo ago First seen · 407 lines · 50 tokens per session scan A 40718986ce4d
analyze-issue is a skill published in the GitHub repository apache/shardingsphere (20,817 stars, last pushed today), licensed Apache-2.0. It adds 50 tokens to every session and 5,350 once invoked, about $0.0002 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 skills, from other repositories
360-feedback-system
360 feedback register: reviewer, subject, review cycle, visibility, due date and score, as CSV, SQL, JSON Schema or Notion on request. Use for 360 reviews or peer feedback cycles.
alumni-re-hire-tracker
Alumni and re-hire register: former role, last working day, re-hire eligibility, current employer and re-engagement date, as CSV, SQL, JSON Schema or Notion on request. Use for alumni outreach.
announcement-board
Announcement board: author, category, department, priority, audience, publish and expiry dates, status and acknowledgements, as CSV, SQL, JSON Schema or Notion on request. Use for internal notices.
redux-to-swr
Migrate React components from Redux + Saga to SWR hooks. Use when converting data fetching from Redux store (reducers, sagas, selectors, connect HOC) to SWR-based hooks in CockroachDB DB Console or cluster-ui.
mma-investigator
Expert system for investigating MMA (Multi-Metric Allocator) behavior on CockroachDB clusters. Helps oncall engineers diagnose load imbalances, understand rebalancing decisions, and identify why MMA did or didn't act.
react-class-to-functional
Convert React class components to functional components with hooks.