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 open-source-readinessgit 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/open-source-readiness)<a href="https://agentmods.dev/skills/migmcc/agent-skill-quality-gate/open-source-readiness"><img src="https://agentmods.dev/badge/skills/migmcc/agent-skill-quality-gate/open-source-readiness.svg" alt="Measured on agentmods" 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.00019 | $0.00180 |
| Opus 5 | $0.00010 | $0.00090 |
| Sonnet 5 | $0.00004 | $0.00036 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
open-source-readiness 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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- repo-audit — 92% identical, 6 lines differ
What it actually says
open-source-readiness
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 README fails the readme 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.
- 7d ago First seen · 41 lines · 19 tokens per session scan A d93fe559c7d9
open-source-readiness is a skill published in the GitHub repository migmcc/agent-skill-quality-gate (2 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 180 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 skills, from other repositories
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…
bellwether
Bring the current PR to a mergeable state: CI green, all review comments resolved, no merge conflicts. Self-contained — watches CI, fixes issues, watches again until merge-ready. Use when the user wants to keep a PR green, auto-fix CI, resolve review comments, or says "get this merged".
gwm
Manage git worktrees across any repository with the gwm Rust binary (CLI + ratatui TUI). Use when the user asks to create / list / remove / bootstrap / switch / link worktrees, run a command across worktrees (gwm exec) or reclaim build artifacts (gwm clean), materialise a PR into a worktree (gwm review), drive a…
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…
argot-write-rule
Codify a repo convention argot's built-ins don't cover into a scripted custom rule — a .argot/rules/NAME/rule.toml manifest plus a sandboxed Rhai script that fires exactly like a built-in, gated on a green fixture suite before it ever sees a real diff. Use when the user asks to "write an argot rule for X", "codify…
argot-suggest-rules
Turn a convention argot has already discovered into a scripted custom rule. Runs argot conventions, surfaces the repo's mined placement conventions (where a kind of code lives — "validation in schema files", "DB access only in migrations", "business logic in the service layer, not views") and internal-API vocabulary…