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 ianchesal/tmux-scout-golang --skill releasegit clone --depth 1 https://github.com/ianchesal/tmux-scout-golangWrote 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/ianchesal/tmux-scout-golang/release)<a href="https://agentmods.dev/skills/ianchesal/tmux-scout-golang/release"><img src="https://agentmods.dev/badge/skills/ianchesal/tmux-scout-golang/release/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/ianchesal/tmux-scout-golang/release"><img src="https://agentmods.dev/badge/skills/ianchesal/tmux-scout-golang/release.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.00048 | $0.00624 |
| Opus 5 | $0.00024 | $0.00312 |
| Sonnet 5 | $0.00010 | $0.00125 |
| Haiku 4.5 | $0.00005 | $0.00062 |
Grade A, and why
release 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Skill for tmux-scout-golang
This skill guides you through creating a new release of tmux-scout-golang. The release process requires a PR (main is branch-protected), so it has two phases: the PR phase and the tag phase.
Step 1: Determine the new version
Read the current version:
cat .version
Parse the version (format: vMAJOR.MINOR.PATCH) and compute the three candidates:
- patch: increment PATCH (e.g. v0.4.2 → v0.4.3)
- minor: increment MINOR, reset PATCH to 0 (e.g. v0.4.2 → v0.5.0)
- major: increment MAJOR, reset MINOR and PATCH to 0 (e.g. v0.4.2 → v1.0.0)
Present the options to the user using AskUserQuestion with three choices showing the computed version number for each type. Wait for their selection before proceeding.
Step 2: Create the release branch and PR
Once the user picks a version type:
- Create a branch:
git checkout -b release/<new-version> - Update
.versionwith the new version string (no trailing newline issues — write exactlyvMAJOR.MINOR.PATCH) - Stage and commit:
git add .version && git commit -m "chore: bump version to <new-version>" - Push:
git push -u origin release/<new-version> - Open a PR with
gh pr create:- Title:
chore: bump version to <new-version> - Body should mention that after merge the user should confirm so the tag can be created
- Title:
Step 3: Wait for merge, then tag
After creating the PR, tell the user:
"PR is open at . Merge it and let me know when it's done — I'll then pull main and run
make tagto create the<new-version>tag and trigger the GitHub release."
When the user confirms the PR is merged:
git checkout main && git pullmake tag
make tag handles everything: verifies the working tree is clean, runs tests, creates the tag, and pushes it to trigger the GitHub Actions release workflow.
Notes
- Never push commits directly to main — branch protection is enforced on the remote.
- The
make tagcommand is authoritative for release preconditions; if it fails, read its error output and fix the issue before retrying. - Version format is always
vMAJOR.MINOR.PATCHwith a lowercasevprefix.
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 · 55 lines · 48 tokens per session scan A edd15f725e65
release is a skill published in the GitHub repository ianchesal/tmux-scout-golang (6 stars, last pushed 2d ago), licensed MIT. It adds 48 tokens to every session and 624 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
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.