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 doodledood/manifest-dev --skill check-prgit clone --depth 1 https://github.com/doodledood/manifest-devWrote 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/doodledood/manifest-dev/check-pr)<a href="https://agentmods.dev/skills/doodledood/manifest-dev/check-pr"><img src="https://agentmods.dev/badge/skills/doodledood/manifest-dev/check-pr/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/doodledood/manifest-dev/check-pr"><img src="https://agentmods.dev/badge/skills/doodledood/manifest-dev/check-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 184 Skill allows unbounded resource consumption (API calls, storage, compute). Without rate limits or quotas, a compromised or misbehaving agent can cause denial-of-service or cost overruns.Fix: Set explicit rate limits, timeouts, and resource quotas for API calls, file operations, and compute. Implement circuit breakers for runaway loops.
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.00083 | $0.03993 |
| Opus 5.5 | $0.00033 | $0.01597 |
| Sonnet 5.5 | $0.00017 | $0.00799 |
| Haiku 4.5 | $0.00008 | $0.00399 |
Grade A, and why
check-pr 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 yesterday.
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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
check-pr
This skill turns the activating session into a read-only PR lifecycle inspector. While it is active, you inspect exactly one GitHub PR, decide whether it is mergeable, and report findings — what's blocking the PR from being mergeable. You never mutate PR or repo state and you never press the merge button. The caller (typically a workflow orchestrator like /do) decides what to do with the findings; this skill does not carry workflow-specific tokens.
Goal
Return PASS when the PR is mergeable; return FAIL with per-gate findings when it isn't. Each finding's Suggested: field carries either a workflow-neutral directive from the fixed vocabulary (a literal GitHub-state action — the caller executes verbatim) or free-form prose describing a solvable-but-novel situation (the caller reads with judgment). Report observable PR state and action targets only; do not decide whether a review comment is substantively correct or what the public reply should say. Do not emit workflow tokens like escalate; that's the caller's call, made by reading findings.
Inputs
- PR URL — canonical
github.com/owner/repo/pull/N(acceptgh:owner/repo/Nandowner/repo#Nas equivalent). - Branch name — the PR's head branch (optional; derivable from the PR).
- Steering — optional plain-English overlay (extra gates, named approvers, known-flaky CI, wait-duration overrides, custom bot routing). Parse with judgment; no schema. When steering itself is ambiguous, surface the ambiguity in the relevant gate's
Reason:as a prose finding rather than guessing.
Canonical gates (the baseline)
The PR is ready when each gate holds:
- PR exists — exactly one open PR on the named branch.
- CI green — required checks pass on the current head commit.
- Review feedback addressed — inbound review feedback has been inspected through its latest reply. That inbox is: open review threads; non-empty review bodies of each author's latest submitted
CHANGES_REQUESTEDorCOMMENTEDreview; inbound human top-level PR comments; and comments stamped<!-- manifest-dev:review-pr -->(the marker is an inbox signal, not a skip). Skip empty, pending, dismissed, and superseded reviews; skipAPPROVEDbodies; skip unthreaded GitHub-App IssueComments (bot nits that arrive as threads still count). A thread is addressed when it is resolved, replied to, or addressed by a follow-up commit on the current head. A review body or top-level comment is addressed when the PR author has later replied on the Conversation, the review is dismissed, or a newer submitted review from the same reviewer supersedes it — a follow-up commit does not address a body or comment. Leave human-authored threads open for their authors to resolve. Do not pass from summary counts or stale state; new pushback or replies keep this gate failing. - Description in sync — PR description reflects the current diff's intent.
- Mergeable — GitHub's current merge state and applicable repository requirements permit the PR to merge. Interpret the returned state under the API's documented semantics; an unknown state remains a wait finding, never a guessed PASS.
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.
- yesterday Changed 0a81d3be6a3e
- 4d ago Changed · +30 lines · +9 tokens per session ec23ed067c51
- 1mo ago Changed a22f7e56ae1c
- 1mo ago First seen · 191 lines · 74 tokens per session scan A 24e4880b4521
check-pr is a skill published in the GitHub repository doodledood/manifest-dev (76 stars, last pushed yesterday), licensed MIT. It adds 83 tokens to every session and 3,993 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
deploy-landed
A deployment verification procedure that checks whether the intended code revision is actually running, its environment settings are present, and the product works. A deployment is the process of putting new software on a server or hosting platform.
signing-preflight
Before the first commit of a session, check that commit signing will work — the key is loaded and unlocked — and ask the operator to unlock it once, up front, instead of discovering it after a hundred unsigned commits. Never disables signing silently, never re-signs history without asking. Use at the start of…
stack-pr
Use when breaking a too-big branch into a stack of smaller chained PRs — commit-based default, --smart agent-reshape, gh-stack detection, cross-links. Invoked by /orc:stack-pr and /orc:ship's size gate.
inline-review
Post a real GitHub PR review with line-anchored inline comments; invoked by /orc:code-review after findings. For commenting on your OWN diff, prefer the bundled /code-review --comment.
triage-aging-prs
Drive an aging pull-request backlog to zero. Inventories every open PR, finds the STRUCTURAL blockers first (a required check that can never run, a reviewer that never fires, chronically red CI), triages every unresolved review thread in parallel and VERIFIES each finding against the code before fixing it, then merges…
review-comments
Systematically pull, categorize, and address all PR review comments — code change requests, questions, and suggestions. This skill fetches comments via gh api, groups them by file, implements fixes, handles disagreements diplomatically, and pushes a single commit. You should not try to handle PR review feedback…