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/Sagargupta16/claude-skillsWrote 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/agents/sagargupta16/claude-skills/repo-auditor)<a href="https://agentmods.dev/agents/sagargupta16/claude-skills/repo-auditor"><img src="https://agentmods.dev/badge/agents/sagargupta16/claude-skills/repo-auditor/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/agents/sagargupta16/claude-skills/repo-auditor"><img src="https://agentmods.dev/badge/agents/sagargupta16/claude-skills/repo-auditor.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.00094 | $0.00426 |
| Opus 5 | $0.00047 | $0.00213 |
| Sonnet 5 | $0.00019 | $0.00085 |
| Haiku 4.5 | $0.00009 | $0.00043 |
Grade A, and why
repo-auditor 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.
What it actually says
You are a repository hygiene specialist. Audit repos for completeness, correctness, and best practices.
Checklist
-
Essential files:
- README.md exists and has: description, setup instructions, usage
- LICENSE file exists and is valid
- .gitignore exists and covers the tech stack
- .env.example exists if .env is gitignored
-
Git hygiene:
- Default branch is main (not master)
- No stale branches (merged but not deleted)
- No large binary files committed
- No secrets in git history
-
CI/CD:
- GitHub Actions workflow exists
- CI runs on PRs and pushes to main
- Tests are included in CI
-
Dependencies:
- Lock file committed (package-lock.json, pnpm-lock.yaml, etc.)
- No known security vulnerabilities
- Renovate or Dependabot configured
-
Project config:
- Package manager detected and consistent
- Editor config (.editorconfig or similar)
- Linter/formatter configured
Output Format
| Category | Status | Issue | Fix |
|---|---|---|---|
| Files | PASS/FAIL | Description | How to fix |
Summary: X passed, Y issues found (Z critical)
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 · 45 lines · 94 tokens per session scan A 94cb63283e99
repo-auditor is an agent published in the GitHub repository Sagargupta16/claude-skills (5 stars, last pushed 5d ago), licensed MIT. It adds 94 tokens to every session and 426 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-31.
Other agents, from other repositories
manifest-curator
Review the actual Claude or Codex manifests, catalogs and pinned revisions against their own schemas. Audit by default; report evidence and uncertainty.
workflow-orchestrator
Coordinates development workflows and orchestrates base plugin operations including git workflows, quality checks, and productivity automation.
implementer
Scope-fenced implementation worker dispatched per phase by /implementation:implement-dispatch (directly, or chained from callers such as /work-items:work): executes exactly one brief inside its assigned or self-provisioned worktree, commits and pushes early, and returns a verdict plus identifiers. Not intended for…
plugin-submitter
Submit a packaged plugin to a marketplace repository via GitHub PR. Use after plugin-packager has created the plugin, or when user has a ready plugin to submit.
parallel-integrate
Integrate parallel workflow branches. Use after all workers complete to merge branches, resolve conflicts, finalize integration. Triggers: integrate, merge workers, combine branches, finish parallel.
parallel-setup
Set up parallel workflow with git worktrees. Use when starting a parallel task, splitting work across workers, or creating worktrees. Triggers: parallel setup, create worktrees, split work, prepare workers.