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 manishiitg/coding-agent-loop --skill release-pr-quality-gategit clone --depth 1 https://github.com/manishiitg/coding-agent-loopWrote 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/manishiitg/coding-agent-loop/release-pr-quality-gate)<a href="https://agentmods.dev/skills/manishiitg/coding-agent-loop/release-pr-quality-gate"><img src="https://agentmods.dev/badge/skills/manishiitg/coding-agent-loop/release-pr-quality-gate/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/manishiitg/coding-agent-loop/release-pr-quality-gate"><img src="https://agentmods.dev/badge/skills/manishiitg/coding-agent-loop/release-pr-quality-gate.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.00041 | $0.00686 |
| Opus 5.5 | $0.00016 | $0.00274 |
| Sonnet 5.5 | $0.00008 | $0.00137 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
release-pr-quality-gate 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 1mo 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release and PR Quality Gate
Outcome
Create an auditable decision workflow that binds an exact change/build to required Browser QA suites, evaluates completeness and policy, and publishes pass, fail, or needs_review with evidence.
When to use
Use after the required suites have passed independently and can run unattended against a uniquely identified preview or release candidate. Use scheduled monitoring for time-based deployed-health checks.
Discovery and user direction
Inspect the current workflow, goals, metrics, configuration, capabilities, stores, reports, and triggers before proposing changes. Summarize reusable design and gaps, then ask focused questions for unresolved customer choices such as scope, success, approvals, thresholds, ownership, and budgets. Record the answers as customer direction. Installation alone does not approve workflow changes or execution. Default to one small-team workflow; split only for incompatible access or lifecycle boundaries.
Required inputs
Resolve trigger type, repository/change/build/environment identity, required suites and groups, route selections, blocking and review rules, timeout/cancellation behavior, evidence retention, duplicate-run policy, and authorized status/report destinations.
Plan and AgentWorks tools
Use deterministic preparation and finalization for identity, expected-suite set, completeness, and verdict derivation. Run existing suite routes rather than copying their tests. Persist needs_review decisions for later review and let a separate finalization action consume the durable decision. Configure authenticated API triggers through the supported Setup surface and integrations.
Knowledge and persistence
Persist gate, suite-run, decision, evidence, and delivery receipts keyed by exact change/build identity and policy revision. Keep canonical tests in their source packages and reusable application facts in KB notes. Never treat attempted delivery as a published status.
Validation and reporting
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 52 lines · 41 tokens per session scan A d6582baf5126
release-pr-quality-gate is a skill published in the GitHub repository manishiitg/coding-agent-loop (13 stars, last pushed 19d ago), licensed MIT. It adds 41 tokens to every session and 686 once invoked, about $0.0002 per session on Opus 5.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-09-14.
Other skills, from other repositories
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
release
Publish a herdr-gpui release. Use when the user asks to cut, push, ship, or publish a release, or to approve, verify, or GPG-sign one that is already running. Covers just release, the protected environments the run stops at, and the local verification and signing steps that are not part of CI.
release-cut
Cut a new pi-agent-dashboard release: promote ## [Unreleased] in CHANGELOG.md, bump every workspace package.json per SemVer, commit, tag v , and push — triggering the Release workflow that publishes every non-private workspace, builds the Electron artifacts, and creates a GitHub Release. Use on "cut a release"…
ship-workflow
Resumable shipping lifecycle: reconciles current Git and GitHub facts from any entry (dirty default or feature branch, local commits, published branch, open PR, existing manual or native stack, merged work), commits dirty work as lossless logical commits, publishes or reuses the PR, requires current CI and review…
release-revoke
Revoke or rollback a pi-agent-dashboard release: delete the GitHub Release, remove the git tag locally and on origin, deprecate the npm version (npm unpublish is blocked after 72h), and optionally revert the release commit. Use when the user says "revoke release", "rollback release", "delete release", "unpublish…
run-dashboard-e2e-local-changes
Run Playwright E2E (tests/e2e/) against the docker/ all-in-one harness so it reflects LOCAL code changes, not a stale cached image.