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.
npx skills add migmcc/agent-skill-quality-gate --skill repo-auditgit clone --depth 1 https://github.com/migmcc/agent-skill-quality-gateWrote 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/migmcc/agent-skill-quality-gate/repo-audit)<a href="https://agentmods.dev/skills/migmcc/agent-skill-quality-gate/repo-audit"><img src="https://agentmods.dev/badge/skills/migmcc/agent-skill-quality-gate/repo-audit/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/migmcc/agent-skill-quality-gate/repo-audit"><img src="https://agentmods.dev/badge/skills/migmcc/agent-skill-quality-gate/repo-audit.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.00018 | $0.00177 |
| Opus 5.5 | $0.00007 | $0.00071 |
| Sonnet 5.5 | $0.00004 | $0.00035 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
repo-audit 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 2mo 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.
This is a copy
92% identical to open-source-readiness — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
repo-audit
Purpose
Audit a public repository for open-source readiness, checking license, README, contributing guide and security policy before the repository is published.
When to use
Use when preparing a repository to go public and you need to confirm it meets open-source readiness standards.
Inputs
- A path to the repository to audit.
Outputs
- A readiness checklist with pass/fail per item.
Acceptance criteria
- Every readiness item is reported with a pass/fail status.
Examples
Audit ./my-repo and return the readiness checklist.
Limitations
- Does not fix issues; it only reports them.
Test cases
- TC-1: a repo missing a LICENSE fails the license item.
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.
- 2mo ago First seen · 41 lines · 18 tokens per session scan A b3d4d8c0c606
repo-audit is a skill published in the GitHub repository migmcc/agent-skill-quality-gate (2 stars, last pushed 13d ago), licensed MIT. It adds 18 tokens to every session and 177 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to open-source-readiness, differing in 6 lines, and is treated as a copy.
Other skills, from other repositories
crit-cli
Use when an agent needs to author or reply to crit inline comments programmatically (including multi-agent workflows commenting on shared code/plans/docs/proposals), publish or unpublish a crit review with crit share, sync a crit review to or from a GitHub PR or GitLab MR, or read/interpret a crit review JSON file.…
crit
Review code changes, a plan, a live page (running dev server), or a local HTML file with Crit inline comments and structured human feedback. Use only when the user explicitly invokes /crit or directly asks to use Crit; a generic review request does not count.
crit-story
Author a crit story and continue the interactive review loop only when the user explicitly invokes crit-story or directly asks you to generate a crit story. Do not infer this skill from generic review, PR, or diff-review requests.
tool-og-render
Render inline SVG to 1200x630 PNG for OG meta tags. rsvg-convert primary path, cairosvg fallback. Bundled with mainbranch PyPI package.
argot-setup
Set argot up for a repository end to end — audit its history, decide what should shape its voice, fit, verify the fit actually catches things, tune the rules its own history says are noisy, and wire the places it runs (pre-write hook, pre-commit, MCP, CI). One sitting, one decision at a time, each proposed with the…
argot-check
Score your working changes with argot — flag code foreign to this repo's own patterns (unfamiliar dependencies, APIs, constructs), functions the repo already has, code filed in the wrong place, imports that break the repo's layering, and tests weakened, disabled, or deleted alongside a production change — before…