Borrowing it
Nothing to install: this file belongs to MCDxAI/minecraft-dev-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/MCDxAI/minecraft-dev-mcp/main/.claude/skills/repo-sweep/SKILL.mdgit clone --depth 1 https://github.com/MCDxAI/minecraft-dev-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/mcdxai/minecraft-dev-mcp/repo-sweep)<a href="https://agentmods.dev/skills/mcdxai/minecraft-dev-mcp/repo-sweep"><img src="https://agentmods.dev/badge/skills/mcdxai/minecraft-dev-mcp/repo-sweep/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/mcdxai/minecraft-dev-mcp/repo-sweep"><img src="https://agentmods.dev/badge/skills/mcdxai/minecraft-dev-mcp/repo-sweep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- 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.00100 | $0.02337 |
| Opus 5 | $0.00050 | $0.01169 |
| Sonnet 5 | $0.00020 | $0.00467 |
| Haiku 4.5 | $0.00010 | $0.00234 |
Grade A, and why
repo-sweep 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 10d 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo Sweep
Perform a comprehensive pre-production audit of a repository before making it public. This skill systematically checks metadata files, documentation, and development artifacts to ensure the repo is production-ready.
Workflow
1. Initial Repository Scan
Start by understanding the repository structure and project type(s):
# Get repository overview
ls -la
find . -type f -name "*.json" -o -name "*.toml" -o -name "*.mod" -o -name "go.mod" | head -20
Identify all project types present (can be multiple in monorepos):
- Fabric Minecraft mod: Look for
fabric.mod.json,gradle.properties - Node/npm: Look for
package.json,package-lock.json - Go: Look for
go.mod,go.sum - Python: Look for
pyproject.toml,setup.py,requirements.txt,uv.lock - Other: Check for project-specific metadata files
2. Metadata Audit
For each project type found, audit metadata files for correctness. The expected username is GhostTypes and organization names should be verified with the user.
Fabric Minecraft Mods
Check fabric.mod.json:
cat fabric.mod.json
Verify:
"authors": Should include "GhostTypes""contact": URLs should use correct GitHub username"sources": Should point to correct repository URL"homepage": Should use correct username/org"issues": Should point to correct repository issues
Check gradle.properties:
cat gradle.properties
Verify:
maven_group: Should use correct organization (e.g.,io.github.ghosttypes)- Any URLs or author fields
Node/npm Projects
Check package.json:
cat package.json
Verify:
"name": Should follow correct naming convention with org scope if applicable"author": Should be "GhostTypes" or include correct details"repository": URL should use correct GitHub username"bugs": URL should point to correct repository"homepage": Should use correct username/org- Any other URL fields
Critical: Check for package-lock.json:
ls -la package-lock.json
git check-ignore package-lock.json
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.
- 10d ago First seen · 270 lines · 100 tokens per session scan A f0f801df7ef3
repo-sweep is a skill published in the GitHub repository MCDxAI/minecraft-dev-mcp (38 stars, last pushed 1mo ago), licensed MIT. It adds 100 tokens to every session and 2,337 once invoked, about $0.0005 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-30.
Other skills, from other repositories
polish-docs-meta
Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
release-and-publish
Ship a release end-to-end across every registry this project targets (npm, MCP Registry). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already complete — this skill is the post-wrapup…
publish-release
Releases a new McpOrchestrator version end to end — version bump PR, tag, and the automated deploy to GitHub Releases, NuGet, and the MCP Registry. Use when asked to release, publish, deploy, ship, or bump the version of McpOrchestrator.
release-notes
Writes user-facing release notes from a git commit range. Use when asked to draft release notes, a changelog entry, or "what's new" text for a release.
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). Verify, commit. Stops at "committed locally on main" — or, when the project releases through a release PR, at "release branch pushed, PR open". No tag, no push to…