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 strikersam/autonomous-ai-agency --skill branch-cleanupgit clone --depth 1 https://github.com/strikersam/autonomous-ai-agencyWrote 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/strikersam/autonomous-ai-agency/branch-cleanup)<a href="https://agentmods.dev/skills/strikersam/autonomous-ai-agency/branch-cleanup"><img src="https://agentmods.dev/badge/skills/strikersam/autonomous-ai-agency/branch-cleanup/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/strikersam/autonomous-ai-agency/branch-cleanup"><img src="https://agentmods.dev/badge/skills/strikersam/autonomous-ai-agency/branch-cleanup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 107 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 121 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 172 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00053 | $0.01232 |
| Opus 5 | $0.00026 | $0.00616 |
| Sonnet 5 | $0.00011 | $0.00246 |
| Haiku 4.5 | $0.00005 | $0.00123 |
Grade A, and why
branch-cleanup scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -o /dev/null -w "%{http_code}" -X DELETE \ How it starts
The opening of the file, as written. The whole thing — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: branch-cleanup
When to Use
Run this skill:
- After merging any feature/fix branch into master
- After a release, when multiple branches have been absorbed
- Any time
git branch -ashows branches beyondmasterandgh-pages
Protected branches — never delete:
mastergh-pages(GitHub Pages deployment)
Step 1 — Confirm master is up to date
git fetch origin
git status
Make sure you are on master and Your branch is up to date with 'origin/master'.
If not, push first before touching branches.
Step 2 — List all remote branches
git branch -r | grep -v 'origin/master\|origin/gh-pages\|origin/HEAD'
For each branch listed, check whether it is fully merged:
git log origin/master..origin/<branch-name> --oneline
- Empty output → fully merged, safe to delete.
- Commits listed → unmerged work; merge it into master first (see Step 3), then return here.
Step 3 — Merge any unmerged branches (if needed)
For each branch with unmerged commits:
git merge --no-ff origin/<branch-name> -m "Merge branch '<branch-name>'"
Resolve any conflicts (keep HEAD for code files; merge both sides for docs/changelog.md).
Run tests before committing the merge:
pytest -x -q
Then push:
git push origin master
Step 4 — Delete merged branches
Option A — git push (standard)
git push origin --delete <branch-name>
Repeat for every merged branch. If this returns 204 or succeeds, you are done.
Option B — GitHub API (use when git push --delete returns 403)
This happens when the git remote is proxied and lacks delete-refs permission.
Requires a GitHub PAT with repo scope (or delete_head_branch permission).
curl -s -o /dev/null -w "%{http_code}" -X DELETE \
-H "Authorization: token <GITHUB_PAT>" \
-H "Accept: application/vnd.github+json" \
"https://api.github.com/repos/<owner>/<repo>/git/refs/heads/<branch-name>"
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.
- 9d ago First seen · 189 lines · 53 tokens per session scan A 088b1413eb32
branch-cleanup is a skill published in the GitHub repository strikersam/autonomous-ai-agency (8 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 1,232 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.
audit-trail
Full traceability from PRD to code commit through the CCPM spec-driven pipeline.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
checkpoint-management
Git-backed state management for safe rollback. Create and restore checkpoints with tagged commits and metadata tracking.
issue-tracking
Track beads as git-backed issues with persistent attribution, supporting Gas Town's bead lifecycle and convoy progress monitoring.