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 ThiagoGuislotti/copilot-instructions --skill release-closeout-engineergit clone --depth 1 https://github.com/ThiagoGuislotti/copilot-instructionsWrote 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/thiagoguislotti/copilot-instructions/release-closeout-engineer)<a href="https://agentmods.dev/skills/thiagoguislotti/copilot-instructions/release-closeout-engineer"><img src="https://agentmods.dev/badge/skills/thiagoguislotti/copilot-instructions/release-closeout-engineer.svg" alt="Measured on agentmods" 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.00285 |
| Opus 5 | $0.00024 | $0.00143 |
| Sonnet 5 | $0.00010 | $0.00057 |
| Haiku 4.5 | $0.00005 | $0.00028 |
Grade A, and why
release-closeout-engineer 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 8d 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
Release Closeout Engineer
Load context first
.github/AGENTS.md.github/copilot-instructions.md.github/instructions/super-agent.instructions.md.github/instructions/feedback-changelog.instructions.md.github/instructions/readme.instructions.md(when README files are in scope)- Active plan from
planning/active/
Claude-native execution
Run as a general-purpose agent within the Super Agent pipeline. Always the last stage before planning update.
Responsibilities
- Determine whether README updates are required and produce final content when they are.
- Prepare a commit message suggestion in English using repository commit conventions.
- Prepare and apply changelog-ready content when the change belongs in version history.
- Keep closeout artifacts concise, accurate, and aligned with the implemented scope.
Output contract
- Closeout summary
- README actions or confirmation that no update is needed
- Structured README updates when files must be rewritten
- Suggested commit message
- Changelog summary and structured update payload
- Ready-to-commit flag
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.
- 8d ago First seen · 35 lines · 48 tokens per session scan A 494867904fe4
release-closeout-engineer is a skill published in the GitHub repository ThiagoGuislotti/copilot-instructions (2 stars, last pushed 2mo ago), licensed MIT. It adds 48 tokens to every session and 285 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
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
changelog
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
git-workflow
Guides you through Git workflows — branching strategies, commit conventions, merge conflict resolution, and release management. Use when working with Git repositories or when the user asks about version control best practices.
development-workflow
Detailed development workflow with modular patterns for git, review, testing, and deployment.
git-push
A GitHub publishing workflow that handles first-time uploads, routine updates, and tagged releases. Git is a system for recording code changes, while GitHub hosts repositories and releases online.