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 justincampbell/gh-watch --skill watch-taggit clone --depth 1 https://github.com/justincampbell/gh-watchWrote 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/justincampbell/gh-watch/watch-tag)<a href="https://agentmods.dev/skills/justincampbell/gh-watch/watch-tag"><img src="https://agentmods.dev/badge/skills/justincampbell/gh-watch/watch-tag/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/justincampbell/gh-watch/watch-tag"><img src="https://agentmods.dev/badge/skills/justincampbell/gh-watch/watch-tag.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.00062 | $0.01139 |
| Opus 5 | $0.00031 | $0.00570 |
| Sonnet 5 | $0.00012 | $0.00228 |
| Haiku 4.5 | $0.00006 | $0.00114 |
Grade A, and why
watch-tag 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 11d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Watch Tags
Monitor a repository's tags using the gh watch CLI extension. It polls GitHub and emits one JSON event per line to stdout when a new tag appears, which makes it a natural fit for the Monitor tool — each event arrives in the conversation as a notification.
Two modes:
- All new tags —
--match '<glob>'filters tag names (e.g.v*). Every new matching tag is reported. - Tags containing a commit —
--contains <sha>reports only tags whose commit includes<sha>in its history. This answers "which release includes my merged commit?" If such a tag already exists when watching starts, it is reported immediately with"preexisting": true.
Prerequisites
Check if the extension is installed:
gh watch --help
If not installed:
gh extension install justincampbell/gh-watch
Usage
Run with the Monitor tool (not Bash with run_in_background). The first notification is the initial-state snapshot; subsequent notifications are tag-created events.
Wait for the release tag that includes a merged commit, then exit:
command:gh watch tag --match 'v*' --contains <sha> --exit-on tag-createddescription:Release tag containing <short-sha>persistent:falsetimeout_ms:7200000(2 hours — raise/lower based on how long releases take)
Watch for every new release tag for the rest of the session:
command:gh watch tag --match 'v*'description:New v* tagspersistent:true(no timeout — stop withTaskStopor end of session)
Composing with gh watch commit
A tag-created event tells you the tag exists — not that its CI or deploy finished. To follow what happens after the tag, take the sha from the tag-created event and hand off to the commit watcher:
gh watch commit <tag-sha> --exit-on ci-passed,ci-failed
Flags
| Flag | Description | Default |
|---|---|---|
--match <glob> |
Filter tag names (*, ?, […]) |
all tags |
--contains <sha> |
Only report tags whose commit contains this commit | |
--interval <duration> |
Polling interval | 60s |
--exit |
Exit after any state change | false |
--exit-on <events> |
Exit after specific event types (comma-separated) |
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.
- 11d ago First seen · 97 lines · 62 tokens per session scan A ce35a3e4c0e9
watch-tag is a skill published in the GitHub repository justincampbell/gh-watch (4 stars, last pushed 23d ago), licensed MIT. It adds 62 tokens to every session and 1,139 once invoked, about $0.0003 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
developer-release
Release management, changeset workflow, firewall log parsing, breaking CLI change rules, and Go module summaries for gh-aw.
versioning-policy
Semver versioning rules for Squad SDK and CLI — prevents prerelease version incidents.
squad-version-check
Internals of how @bradygaster/squad-cli stamps its version, how squad upgrade works (what it preserves vs overwrites), and how to probe the npm registry for the latest version from a coordinator prompt.
awf-release-integrator
Upgrade gh-aw to latest gh-aw-firewall release and identify follow-up spec tasks.
release-process
Pre-release validation, npm publish procedures, and post-publish verification.
git-workflow
Squad branching model: dev-first workflow with insiders preview channel.