Borrowing it
Nothing to install: this file belongs to starSumi/Sumi-Docs-MCP. 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/starSumi/Sumi-Docs-MCP/main/.agents/skills/sumi-docs-pr/SKILL.mdgit clone --depth 1 https://github.com/starSumi/Sumi-Docs-MCPWrote 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/starsumi/sumi-docs-mcp/sumi-docs-pr)<a href="https://agentmods.dev/skills/starsumi/sumi-docs-mcp/sumi-docs-pr"><img src="https://agentmods.dev/badge/skills/starsumi/sumi-docs-mcp/sumi-docs-pr/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/starsumi/sumi-docs-mcp/sumi-docs-pr"><img src="https://agentmods.dev/badge/skills/starsumi/sumi-docs-mcp/sumi-docs-pr.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.00057 | $0.00540 |
| Opus 5 | $0.00028 | $0.00270 |
| Sonnet 5 | $0.00011 | $0.00108 |
| Haiku 4.5 | $0.00006 | $0.00054 |
Grade A, and why
sumi-docs-pr 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 11d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- sumi-docs-pr — 98% identical, 6 lines differ
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.
Prepare a Sumi Docs Pull Request
Read the root and nearest nested AGENTS.md, CONTRIBUTING.md, and the current
pull request template. Inspect live Git status, the diff, and the base branch;
preserve unrelated work and never infer a clean tree from an earlier report.
Classify the record before implementation
- Use a direct pull request for a narrow correction or internal change that preserves public behavior.
- Open a proposal issue before changing a public contract, architecture, security boundary, production dependency, locale or route model, deployment, or host integration.
- Update the product requirements document for durable product scope.
- Record an accepted, durable tradeoff as an ADR in the owning decision directory. Do not use an ADR as a work log.
- Put executable specifications in schemas, TypeScript types, tool schemas, and conformance tests. Do not maintain a prose duplicate of a machine contract.
- Add or update a reproducible benchmark when a performance claim or threshold changes; generated benchmark evidence belongs to CI artifacts.
- Route vulnerabilities through
SECURITY.mdand a private GitHub advisory. Never open a public CVE placeholder or public vulnerability issue.
Verify the net change
Map changed paths to their owning workspace. Run the smallest relevant red test first, then the owning package checks. Before declaring the branch ready, run from the repository root:
pnpm run verify
pnpm run verify:integration
For content changes, require both locales, the reviewed content catalog, fresh translation-pair records after human semantic review, and a Web-to-MCP URL round trip. For a public contract change, update active documentation, examples, tests, and the changelog together. Report every failed or skipped gate.
Draft the pull request
Use a Conventional Commit-style title. Explain why the net change is needed before what changed. Include compatibility and security impact, focused test evidence, documentation impact, and an exact rollback. Use repository-relative paths and omit local paths, credentials, private corpus data, agent attribution, and abandoned implementation attempts.
What ships with it
1 file 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.
- 11d ago First seen · 57 lines · 57 tokens per session scan A 8bf56b8ce6e8
sumi-docs-pr is a skill published in the GitHub repository starSumi/Sumi-Docs-MCP (1 stars, last pushed 2d ago), licensed MIT. It adds 57 tokens to every session and 540 once invoked, about $0.0003 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 skills, from other repositories
draft-release-notes
Author the committed release-notes file for a Prisma 8 release (stable or 8.0.0-rc.N) by enumerating the merged PRs since the previous release v tag (stable or -rc.N), resolving opaque TML-NNNN: titles via Linear context (never copied verbatim), triaging public-worthiness, and writing categorized notes — breaking…
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
triage-contributor-pr
Triage open pull requests from external contributors to prisma/prisma and produce a per-PR verdict with evidence. Use when a maintainer asks to triage, evaluate, assess, or review the queue of incoming contributor PRs, to decide whether a fork PR is safe to run CI on, to check whether a PR is in scope for its version…
contrib-pr
Open a high-quality external contributor PR against prisma/orm. Use when the user is an outside contributor (not a Prisma maintainer) and wants to submit a change as a pull request from a fork. Encodes the contribution flow from CONTRIBUTING.md so the resulting PR passes review on the first round.
publish-npm-version
Cuts the next release of Prisma 8: bumps the root package.json version (on the v8 RC line: 8.0.0-rc.N → rc.N+1), propagates it to every workspace package, and opens a PR titled "chore(release): bump to ". When the maintainer merges the PR, the Publish to npm workflow runs automatically and ships the new version to npm…
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.