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 paultyng/skill-issue --skill push-and-watchgit clone --depth 1 https://github.com/paultyng/skill-issueWrote 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/paultyng/skill-issue/push-and-watch)<a href="https://agentmods.dev/skills/paultyng/skill-issue/push-and-watch"><img src="https://agentmods.dev/badge/skills/paultyng/skill-issue/push-and-watch.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.00049 | $0.00452 |
| Opus 5 | $0.00024 | $0.00226 |
| Sonnet 5 | $0.00010 | $0.00090 |
| Haiku 4.5 | $0.00005 | $0.00045 |
Grade A, and why
push-and-watch 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 8d 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.
What it actually says
Push and Watch
Push local commits to the remote and monitor the CI run until completion.
1. Pre-flight Checks
- Verify the working tree is clean (
git status). If there are uncommitted changes, stop and ask. - Verify there are local commits ahead of the remote (
git statusshould show "Your branch is ahead"). If not, report "nothing to push" and stop.
2. Push
git push -u origin HEAD
If the push fails (e.g. rejected, no access), stop and report the error.
3. Ensure Pull Request Exists
Skip this step if on main or master.
Check whether a PR already exists for the current branch:
gh pr view --json url 2>/dev/null
If no PR exists, create one in draft mode:
gh pr create --draft --fill
Report the PR URL.
4. Wait for Run
Wait a few seconds for CI to pick up the push, then list runs for the current branch:
gh run list --branch $(git branch --show-current) --limit 1
If no run appears after 30 seconds of polling, report and stop.
5. Watch
Use gh run watch <run_id> --exit-status to stream the run status until completion.
6. Report
After the run completes, report:
- Status: passed or failed
- Jobs: list each job with its status and duration
- Failures: if any job failed, fetch its logs with
gh run view <run_id> --log-failedand include the relevant error output (truncated to the last 50 lines per failed job)
If the run passed, report success concisely. If it failed, include enough log context to diagnose the failure.
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.
- 8d ago First seen · 64 lines · 49 tokens per session scan A 5c106d1d0625
push-and-watch is a skill published in the GitHub repository paultyng/skill-issue (9 stars, last pushed 27d ago), licensed MIT. It adds 49 tokens to every session and 452 once invoked, about $0.0002 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
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
turborepo-caching
Configure Turborepo for efficient monorepo builds with local and remote caching. Use when setting up Turborepo, optimizing build pipelines, or implementing distributed caching.
ship
Verify and publish by pushing, opening a PR, and watching CI; land mode merges then cleans branches. Triggers "ship it", "create PR", "/ship", "watch the PR", "babysit CI"; land mode "land it", "/ship land", "fix CI and merge".
shared-tooling-git-hooks
Husky v9 setup, lint-staged v16 patterns, commitlint with conventional commits, CI/production handling, monorepo setup, migration from v8.
lov-release-via-cicd
A release workflow for Node, Tauri, Vite, shell, and GitHub Release projects. It checks or configures automated versioning and publishing, including macOS signing and notarisation when relevant.
ci-cd-ops
CI/CD pipeline patterns with GitHub Actions, release automation, and testing strategies. Use for: github actions, workflow, CI, CD, pipeline, deploy, release, semantic release, changesets, goreleaser, matrix, cache, secrets, environment, artifact, reusable workflow, composite action.