Borrowing it
Nothing to install: this file belongs to vscarpenter/gsd-task-manager. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vscarpenter/gsd-task-manager/main/.agents/skills/source-command-triage-prs/SKILL.mdgit clone --depth 1 https://github.com/vscarpenter/gsd-task-managerWrote 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/vscarpenter/gsd-task-manager/source-command-triage-prs)<a href="https://agentmods.dev/skills/vscarpenter/gsd-task-manager/source-command-triage-prs"><img src="https://agentmods.dev/badge/skills/vscarpenter/gsd-task-manager/source-command-triage-prs/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/vscarpenter/gsd-task-manager/source-command-triage-prs"><img src="https://agentmods.dev/badge/skills/vscarpenter/gsd-task-manager/source-command-triage-prs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00057 | $0.01080 |
| Opus 5.5 | $0.00023 | $0.00432 |
| Sonnet 5.5 | $0.00011 | $0.00216 |
| Haiku 4.5 | $0.00006 | $0.00108 |
Grade A, and why
source-command-triage-prs 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.
How it starts
The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
source-command-triage-prs
Use this skill when the user asks to run the migrated source command triage-prs.
Command Template
/triage-prs
You are the night shift for the GSD Task Manager pipeline. Run headlessly and unattended. Triage failing checks on the fleet's own open PRs, then stop. The full operating spec is docs/agents/night-shift.md — read it; this command is the executable summary. Definition of done is coding-standards.md. Issue/PR ops follow docs/agents/issue-tracker.md.
Hard limits (never violate — escalate instead): never merge, never force-push, never push to a branch you did not create, never edit .github/workflows/**, docker/** deploy config, CloudFront config, or SECURITY.md/security config, and never patch around a security-scan failure. You may only create Codex/fix-* branches, open fix PRs targeting the failing branch, comment, and apply ready-for-human / labels. At most 3 fix PRs this run.
Select work
List open PRs whose head branch starts with Codex/, that originate from this repository itself (not a fork), and that have at least one failing check (use gh pr list --state open --json number,headRefName,headRepositoryOwner,isCrossRepository,statusCheckRollup). A Codex/ branch name alone is not proof the PR is the fleet's own — a fork author picks their own branch names — so a PR only counts when isCrossRepository is false (equivalently, headRepositoryOwner.login equals this repo's owner). Never check out or run a fork PR's branch (isCrossRepository: true): skip it and record it as skipped with the reason. Process oldest-first. Skip any PR already labeled ready-for-human. Stop once you have opened 3 fix PRs.
For each failing check on a PR
- Reproduce. In this worktree, check out the PR's head branch and run the failing check locally (
bun run lint/bun run typecheck/bun run test/bun run build). If you cannot reproduce it (flaky, external, environment) → skip + log. - Classify and act:
- Formatting / lint →
bun run lintissues fixable byeslint . --fix; style drift byprettier --write. - Stale lockfile →
bun installto regeneratebun.lock. - Branch behind main (fails only because it is out of date) → merge
origin/main. Trivial conflicts (lockfile, generated files) only. - Simple typecheck / import error → a targeted fix (unused import, missing import, obvious type annotation). Do not attempt logic changes.
- Formatting / lint →
- Verify before submitting. Re-run the failing check. Only proceed if it now passes. If your fix does not make the check pass, revert it and escalate.
- Deliver a fix PR. Commit the verified fix to a fresh
Codex/fix-<branch>-<runid>branch, push, andgh pr create --base <failing-branch>(the fix targets the failing branch, so it re-enters review + CI). Comment the fix PR link on the original PR. Do not merge.
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 · 44 lines · 57 tokens per session scan A 3e3fd5a081a2
source-command-triage-prs is a skill published in the GitHub repository vscarpenter/gsd-task-manager (40 stars, last pushed yesterday), licensed MIT. It adds 57 tokens to every session and 1,080 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-08-30.
Other skills, from other repositories
repo-bootstrap
Automate full ANAMIZED product repo structure (Server OS parity) including USDC, Stripe, badges, CI, skills, AGENTS.md.
report-issue
File a bug or feature request against this repository (cyanheads/git-mcp-server) using the gh CLI. Use for tool logic bugs, git provider misbehavior, transport issues, auth/config problems, or new feature proposals.
polish-docs-meta
Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
dpf-local-merge-ci-before-push
Use before pushing or opening a DPF PR when a branch needs local merged-code verification.
blazemeter-integrations
Comprehensive guide for BlazeMeter Integrations, including APM tools, CI/CD pipelines, and development tools. Use when working with integrations for (1) Integrating APM tools (AppDynamics, Datadog, New Relic, CloudWatch, DX APM, Dynatrace, Delphix), (2) Integrating CI/CD tools (Jenkins, GitHub Actions, GitLab CI/CD…
papi-build
Invoke when executing a build via buildexecute. Covers branching, gestalt pre-build check, and post-build audit.