A repository-maintenance command that checks common project files such as .gitignore, environment-variable examples, the README, and the software licence.

Use it to audit and repair repository setup files, check for exposed secrets, and create a focused commit with the changes.

It helps prevent missing project documentation, unsuitable ignore rules, and accidentally committed passwords or API keys.

polish-repo — Command for Claude Code by Sagargupta16

Install

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.

Clone the repo

git clone --depth 1 https://github.com/Sagargupta16/claude-skills

Made for: Claude Code.

Or install repo-polish, the plugin that ships this one along with the rest of its 1 skill, 1 command, 1 agent.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/sagargupta16/claude-skills/polish-repo/github.svg)](https://agentmods.dev/commands/sagargupta16/claude-skills/polish-repo)

Your own site

<a href="https://agentmods.dev/commands/sagargupta16/claude-skills/polish-repo"><img src="https://agentmods.dev/badge/commands/sagargupta16/claude-skills/polish-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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/sagargupta16/claude-skills/polish-repo"><img src="https://agentmods.dev/badge/commands/sagargupta16/claude-skills/polish-repo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 273 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00017	$0.00273
Opus 5	$0.00009	$0.00137
Sonnet 5	$0.00003	$0.00055
Haiku 4.5	$0.00002	$0.00027

Measured 6d ago against content hash a28e3ebea42b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

polish-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 6d 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.

plugins/repo-polish/commands/polish-repo.md · 28 lines

What it actually says

Audit the current repository and fix any missing or incomplete hygiene files.

Steps:

Sync from remote first: git pull
Detect the project type (Node.js, Python, Unity, academic, etc.)
Audit these files:
- .gitignore -- exists? covers the right patterns for project type?
- .env.example -- needed? (search for process.env or os.getenv usage)
- README.md -- exists? has meaningful content (not just the repo name)?
- LICENSE -- exists?
For each missing/incomplete item:
- Generate appropriate content using the repo-polish skill templates
- Show what will be created/changed
Check for committed secrets:
- Search for .env files with real values
- Search for hardcoded API keys or passwords
- Flag any findings as critical
Stage specific files (never git add .)
Commit with: chore: add missing repo hygiene files
Show summary of all changes made

Use the repo-polish skill for all templates and patterns. Never commit .env files with real credentials.

Changes

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.

6d ago Changed a28e3ebea42b
12d ago First seen · 28 lines · 17 tokens per session scan A 6a3fe854ca0c

Subscribe to this mod's changes

polish-repo is a command published in the GitHub repository Sagargupta16/claude-skills (5 stars, last pushed 6d ago), licensed MIT. It adds 17 tokens to every session and 273 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.

Claude Code Git and workflow ai-agents claude developer-tools marketplace plugins

polish-repo

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

commit

speckit.taskstoissues

clean-gone

commit-push-pr

commit

adk-ts-changelog