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 gpsaggese/helpers --skill github.get_pr_to_pass_local_testsgit clone --depth 1 https://github.com/gpsaggese/helpersWrote 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/gpsaggese/helpers/github.get_pr_to_pass_local_tests)<a href="https://agentmods.dev/skills/gpsaggese/helpers/github.get_pr_to_pass_local_tests"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/github.get_pr_to_pass_local_tests/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/gpsaggese/helpers/github.get_pr_to_pass_local_tests"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/github.get_pr_to_pass_local_tests.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.00010 | $0.00664 |
| Opus 5.5 | $0.00004 | $0.00266 |
| Sonnet 5.5 | $0.00002 | $0.00133 |
| Haiku 4.5 | $0.00001 | $0.00066 |
Grade A, and why
github.get_pr_to_pass_local_tests 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goal
- Run, monitor, and fix the local unit tests for the current PR
Workflow
Create and Update a Plan
- Create
plan-github.get_pr_to_pass_local_tests.md: a bullet list of actions - Keep it updated, marking each action
[.]in progress,[x]done,[F]failed
Get the PR Number and Branch Name
-
Get the PR number
> GH_PR_NUM=$(gh pr view --json number -q .number) -
Get the branch name
> BRANCH_NAME=$(git branch --show-current)
Run Local Regressions
- Run full test suite locally:
> pytest_multi_build.py --target . 2>&1 --timeout -1 | tee tmp.auto_task.pytest_multi_build.log - Wait for the script to terminate
Check Regressions to Complete
- Check the output of the local regressions with:
> pytest_failed_multi_build.py 2>&1 | tee tmp.auto_task.pytest_failed_multi_build.log
Report Status on the PR
- If local regressions are passing:
> gh pr comment $GH_PR_NUM --body "Local tests passing" - If any failures, document error and post:
> gh pr comment $GH_PR_NUM --body "Local test failures found: [error summary]. Investigating..."
Fix the Failures
- If failures were found, run
tmp.pytest_failed_multi_build.repro.shto understand what failed and use/pytest.fix_local_teststo analyze and fix them- If the fix is simple, just fix it and commit
- If the fix is not clear, stop and ask for the user to help
Never Commit Junk Files
- Never run
git add -Aorgit add .to stage a fix: they sweep in every untracked file (logs,tmp.*scratch files, test-run artifacts like.pkl/.jsoncaches), not just the intended files - Always stage files explicitly by path, e.g.
git add <file1> <file2> - Before committing, run
git status --shortand drop anything that is not part of the intended fix - If junk was already committed and pushed, amend the commit to hold only the
intended files and force-push (
git push --force-with-lease)
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 First seen · 78 lines · 10 tokens per session scan A da4c49b48aab
github.get_pr_to_pass_local_tests is a skill published in the GitHub repository gpsaggese/helpers (158 stars, last pushed today), licensed Apache-2.0. It adds 10 tokens to every session and 664 once invoked, about $0.0000 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-11-06.
github.get_pr_to_pass_local_tests compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| github.get_pr_to_pass_local_testsgpsaggese/helpers | Skill | 158 | today | Apache-2.0 | A | 10 | Claude Code |
| github-copilot-upgradermicrosoft/vscode | Skill | 195k | today | MIT | A | 18 | Claude Code, Codex |
| merge-queue-readinessZaxbyHub/opencode-swarm | Skill | 517 | today | MIT | A | 39 | OpenCode |
| precommitsd0xdev/sd0x-harness | Skill | 194 | 1mo ago | MIT | A | 15 | Claude Code |
| precommit-fastsd0xdev/sd0x-harness | Skill | 194 | 1mo ago | MIT | A | 15 | Claude Code |
| test-suite-prioritizerArabelaTso/Skills-4-SE | Skill | 260 | 2mo ago | Apache-2.0 | A | 84 | Claude Code, Codex |
| transport-release-gateyzonur/sap-adt-mcp | Skill | 22 | 8d ago | MIT | A | 131 | Claude Code, Codex |