Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/aget-framework/template-advisor-agetnpx agentmods add skills/aget-framework/template-advisor-aget/aget-release-buildWrote 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/aget-framework/template-advisor-aget/aget-release-build)<a href="https://agentmods.dev/skills/aget-framework/template-advisor-aget/aget-release-build"><img src="https://agentmods.dev/badge/skills/aget-framework/template-advisor-aget/aget-release-build/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/aget-framework/template-advisor-aget/aget-release-build"><img src="https://agentmods.dev/badge/skills/aget-framework/template-advisor-aget/aget-release-build.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.00049 | $0.01285 |
| Opus 5.5 | $0.00020 | $0.00514 |
| Sonnet 5.5 | $0.00010 | $0.00257 |
| Haiku 4.5 | $0.00005 | $0.00128 |
Grade A, and why
aget-release-build 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 1mo 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aget-release-build
Execute gate deliverables with the Builder perspective of the Release Delivery Triad (L818). Speed-optimized execution mode.
Purpose
The Builder asks: "Is this done? Is it fast? Does it work?"
This skill shifts your cognitive posture to prioritize execution fidelity, velocity tracking, and mechanical correctness. You are the Builder — move fast, execute cleanly, report completion.
You do NOT audit specifications (that is /aget-release-audit-specs). You do NOT adversarially test assumptions (that is /aget-release-critique). You build.
Triggers
- "build gate", "execute gate"
- "release build mode"
/aget-release-build
Input
Optional: gate number or PROJECT_PLAN path. If omitted, detect the active release PROJECT_PLAN and current gate.
Execution
Step 1: Identify Current Gate
Read the active planning/PROJECT_PLAN_v*.md file. Identify:
- Current gate number and name
- Deliverable checklist (items marked
[ ]) - Estimated time budget for this gate
If no active plan found, report error and stop.
Step 2: Execute Deliverables
For each deliverable in the gate:
- Read the deliverable specification
- Execute it
- Mark
[x]in the plan with a brief finding note - Track elapsed time
Builder rules:
- Execute ONLY the specified deliverables — no scope expansion
- If a deliverable is blocked, note the blocker and move to the next
- If a deliverable reveals a spec gap, note it for the Spec Auditor — do NOT fix the spec yourself
- If a deliverable raises a concern, note it for the Critic — do NOT investigate yourself
Step 3: Velocity Report
After all deliverables are attempted, report:
=== Builder Report: Gate [N] ===
Deliverables: [completed]/[total]
Blocked: [count] ([list blockers])
Time: [actual] vs [estimated] ([velocity]x)
Findings for Spec Auditor:
- [any spec gaps noticed during execution]
Findings for Critic:
- [any concerns or assumptions noticed]
Gate Status: [COMPLETE / BLOCKED / PARTIAL]
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.
- 1mo ago Changed · +5 lines · +49 tokens per session 71a702b6d70f
- 1mo ago First seen · 139 lines · 0 tokens per session scan A 0190b878c7fb
aget-release-build is a skill published in the GitHub repository aget-framework/template-advisor-aget (2 stars, last pushed 8d ago), licensed Apache-2.0. It adds 49 tokens to every session and 1,285 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
pypi-release
This skill should be used when releasing tunacode-cli to PyPI. It keeps the existing local release checks, then hands the actual PyPI upload to a GitHub Actions workflow that uses the repository's PYPIAPITOKEN secret.
python-format
Formats Python files with ruff format and reports which files changed.
changelog-writer
Use when a release is being prepared and a human-readable changelog must be generated from merged pull requests.
metagit-release-audit
Mandatory before calling work complete when the session changed repo files. Runs format, lint, tests, integration tests, context-aware pip-audit/bandit, and optional gitleaks via task qa:prepush. Use before push, release, or hand-off.
skillshare-changelog
Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed…
gh
GitHub CLI skill for interacting with GitHub via the gh command line tool. Use when Bub needs to (1) Create, view, or manage GitHub repositories, (2) Work with issues and pull requests, (3) Create and manage releases, (4) Run and monitor GitHub Actions workflows, (5) Create and manage gists, (6) Install and manage…