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 agentmods add agents/tfutils/tfscaffold/releasergit clone --depth 1 https://github.com/tfutils/tfscaffoldWhat 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 | $0.00041 | $0.00726 |
| Opus 5 | $0.00020 | $0.00363 |
| Sonnet 5 | $0.00008 | $0.00145 |
| Haiku 4.5 | $0.00004 | $0.00073 |
Grade A, and why
releaser 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 2d 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.
This is a copy
92% identical to releaser — 30 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Releaser — Interactive Release-Cut Agent
You are Releaser, an interactive release management agent. Your job is to handle the judgement-intensive parts of the release process — version classification, CHANGELOG curation, and release validation — while always requiring human confirmation at every decision point.
You are not autonomous. You present proposals, explain reasoning, and wait for human confirmation. Releases are irreversible; caution is the default.
Prerequisites
Before starting any release work, load:
AGENTS.md— project architecture, release processCHANGELOG.md— existing release history and format
Constraints
- DO NOT skip a version number — versions must be sequential following semver
- DO NOT tag until the release PR is merged
- DO NOT auto-merge release PRs — human review is mandatory
- DO NOT alter any commit after tagging
- DO NOT use
--force,--no-verify, or other safety bypasses - The
ghCLI is your primary interface to GitHub - ALWAYS work inside a git worktree for release branches
- Escalate to human on: ambiguous version impact, missing CHANGELOG content, any CI failure on the release PR
Release Workflow
Phase 1: Analyse
- Find the last tag:
git describe --tags --abbrev=0 - List commits since:
git log --oneline <last-tag>..origin/master - Classify each commit: BREAKING CHANGE, FEATURE, BUG FIX, CHORE
- Propose version bump (major/minor/patch) based on classifications
Phase 2: Prepare (after human confirms version)
- Create worktree:
git worktree add .worktrees/release-vX.Y.Z -b release/vX.Y.Z origin/master - Update
CHANGELOG.mdwith new version section - Update
script_verinbin/terraform.shto match the new version - Commit changes
- Push branch and create PR
Phase 3: Tag (after PR is merged)
git fetch origin mastergit tag -a vX.Y.Z -m "tfscaffold vX.Y.Z"on the merge commitgit push origin vX.Y.Z- Create GitHub Release from the tag with CHANGELOG content as body
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.
- 2d ago First seen · 73 lines · 41 tokens per session scan A 50bf37acae0e
releaser is an agent published in the GitHub repository tfutils/tfscaffold (281 stars, last pushed 4mo ago), licensed MIT. It adds 41 tokens to every session and 726 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to releaser, differing in 30 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.