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.
git clone --depth 1 https://github.com/davistroy/claude-marketplaceWrote 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/commands/davistroy/claude-marketplace/clean-repo)<a href="https://agentmods.dev/commands/davistroy/claude-marketplace/clean-repo"><img src="https://agentmods.dev/badge/commands/davistroy/claude-marketplace/clean-repo/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/commands/davistroy/claude-marketplace/clean-repo"><img src="https://agentmods.dev/badge/commands/davistroy/claude-marketplace/clean-repo.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.00010 | $0.03477 |
| Opus 5 | $0.00005 | $0.01739 |
| Sonnet 5 | $0.00002 | $0.00695 |
| Haiku 4.5 | $0.00001 | $0.00348 |
Grade A, and why
clean-repo 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 12d 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 — 450 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Cleanup and Organization
Perform a thorough cleanup and organization pass on this repository. This command requires deep analysis of the codebase before any cleanup actions.
Input Validation
Optional Arguments:
--dry-run- Preview all changes without executing them--audit- Log all actions to.claude-plugin/audit.log--docs-only- Skip artifact cleanup, focus only on documentation sync--json- Output results as structured JSON instead of text. Enables CI/CD pipeline integration and programmatic consumption.
Dry-Run Mode:
When --dry-run is specified:
- Perform all analysis phases normally
- Show what files would be deleted, moved, or modified
- Show what documentation updates would be made
- Prefix all proposed actions with
[DRY-RUN] - Do NOT execute any file deletions, moves, or modifications
Audit Mode:
When --audit is specified:
- Log every action to
.claude-plugin/audit.log - Each log entry is a JSON line with: timestamp, command, action, path, success
Phase 0: Deep Repository Analysis (REQUIRED)
CRITICAL: This phase must be completed thoroughly before any cleanup.
Before cleaning or updating anything, you MUST understand what this repository actually contains and does. Use the available tools to build a complete mental model.
0.1 Project Discovery
Execute these analysis steps:
1. Read the root README.md completely
2. Read CLAUDE.md if present
3. Examine the directory structure (use Glob to map all directories)
4. Identify the project type(s): library, CLI tool, plugin, monorepo, etc.
5. Find all package manifests (package.json, pyproject.toml, plugin.json, etc.)
0.2 Feature Inventory
Build a complete list of what this project provides:
For plugins/tools:
- List all commands/skills with their actual functionality
- Read command/skill files to understand what each does
- Note any bundled tools or utilities
For libraries:
- List all exported functions/classes
- Identify the public API surface
- Note major features and capabilities
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.
- 12d ago First seen · 450 lines · 10 tokens per session scan A 3baf1ee63143
clean-repo is a command published in the GitHub repository davistroy/claude-marketplace (5 stars, last pushed 4d ago), licensed MIT. It adds 10 tokens to every session and 3,477 once invoked, about $0.0001 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 commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
handoff
Export a Waybill Bundle by default, or import one when requested.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.