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.
git clone --depth 1 https://github.com/o2alexanderfedin/strategic-research-automation-templateWrote 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/commands/o2alexanderfedin/strategic-research-automation-template/finalize-release)<a href="https://agentmods.dev/commands/o2alexanderfedin/strategic-research-automation-template/finalize-release"><img src="https://agentmods.dev/badge/commands/o2alexanderfedin/strategic-research-automation-template/finalize-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/commands/o2alexanderfedin/strategic-research-automation-template/finalize-release"><img src="https://agentmods.dev/badge/commands/o2alexanderfedin/strategic-research-automation-template/finalize-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.00000 | $0.00461 |
| Opus 5 | $0.00000 | $0.00230 |
| Sonnet 5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
finalize-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 12d 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.
What it actually says
Finalize Release
Objective
Create git release/tag for completed sprint, archive findings, and prepare for next sprint.
Usage
/finalize-release 01
Release Process
1. Verify Sprint Complete
- Confirm all tasks (01-06) are complete
- Verify final report exists
- Check quality validation passed
- Ensure all findings committed to git
2. Create Git Tag
git tag -a sprint-01-complete -m "Sprint 01: [Sprint Name] - Complete
Final Score: [score]/100
Recommendation: [Go/No-Go]
Research Files: [count]
Report Date: [date]"
3. Update CHANGELOG
Add sprint completion to CHANGELOG.md:
## Sprint 01 - [Sprint Name] - [Date]
### Completed
- Technical & Regulatory Landscape Research
- Market & Competitive Assessment
- Solution Architecture Design
- Certification & Testing Strategy
- Implementation Roadmap
- Final Report Synthesis
### Deliverables
- Research files: [count] files in temp/sprint-01/
- Final report: reports/sprint-01-final-report.md
- Opportunity score: [score]/100
- Recommendation: [Go/No-Go with brief rationale]
### Key Findings
- [Key finding 1]
- [Key finding 2]
- [Key finding 3]
4. Archive Research Files (Optional)
If desired, create compressed archive:
tar -czf archives/sprint-01-research.tar.gz temp/sprint-01/
5. Push to Remote
git add .
git commit -m "Sprint 01: Finalize release"
git push origin main
git push --tags
6. Prepare for Next Sprint
- Clear temp/sprint-01/ if desired (or keep for reference)
- Update sprint-config.yml for next sprint
- Review and update context files if needed
Output
- Git tag created:
sprint-01-complete - CHANGELOG updated
- Changes committed and pushed
- Optional: Research archive created
- Repository ready for next sprint
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.
- 12d ago First seen · 79 lines · 0 tokens per session scan A 1d6d280e8523
finalize-release is a command published in the GitHub repository o2alexanderfedin/strategic-research-automation-template (19 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 461 tokens. 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-30.
Other commands, from other repositories
prp-pr
Create a GitHub PR from current branch with unpushed commits — discovers templates, analyzes changes, pushes.
ship
Deploy feature through automated staging validation to production with rollback testing.
release
Automate complete release workflow for Spec-Flow package (version bump, CHANGELOG, git tag, GitHub release, npm publish).
pr
Create a GitHub PR from current branch with unpushed commits — discovers templates, analyzes changes, pushes.
ship
A release command for preparing code changes as separate Git commits, creating release notes, and adding a version tag. Git is a system for tracking code changes, and a tag marks a specific release.
pre-release
Parallel pre-release check — fires release-captain + security-reviewer + code-reviewer simultaneously. Go/no-go in one command before you ship.