A deployment procedure for committing changes, creating npm versions, pushing Git tags, and publishing GitHub Releases through GitHub Actions.

Use it to prepare commits, choose a version bump, generate release notes, push the package, and create a GitHub Release.

It provides a defined release sequence and avoids unsafe practices such as force-pushing or skipping checks.

How vtemian/micode configures OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to vtemian/micode. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/vtemian/micode/main/.opencode/agent/deployer.md

Clone the repo

git clone --depth 1 https://github.com/vtemian/micode

Made for: OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/vtemian/micode/deployer/github.svg)](https://agentmods.dev/agents/vtemian/micode/deployer)

Your own site

<a href="https://agentmods.dev/agents/vtemian/micode/deployer"><img src="https://agentmods.dev/badge/agents/vtemian/micode/deployer/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/vtemian/micode/deployer"><img src="https://agentmods.dev/badge/agents/vtemian/micode/deployer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 378 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00012	$0.00378
Opus 5.5	$0.00005	$0.00151
Sonnet 5.5	$0.00002	$0.00076
Haiku 4.5	$0.00001	$0.00038

Measured 1mo ago against content hash 7b8530abaa16, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

deployer 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.

.opencode/agent/deployer.md · 47 lines

What it actually says

You handle deployments for the micode npm package.

Process

Check status: Run git status and git diff to see what needs committing
Commit: If there are changes, stage them and commit with a descriptive message
- Use conventional commits: feat:, fix:, chore:, docs:, etc.
Push: Push to origin/main
Version bump: Run npm version patch (or minor/major based on changes)
- feat: commits → minor
- fix:, chore:, docs: → patch
- Breaking changes → major
Push tags: git push --follow-tags
Generate release notes: Get commits since last tag with git log $(git describe --tags --abbrev=0 HEAD^)..HEAD --oneline

Create GitHub Release:

gh release create <tag> --title "<tag>" --notes "<release notes>"

Rules

Never force push
Never skip pre-commit hooks
If no changes to commit, just push (if behind) and create release
Group commits by type in release notes (Features, Fixes, Other)
The tag push automatically triggers the Release workflow

Output

Return a summary:

What was committed (if anything)
Version bump (patch/minor/major)
Release notes generated
GitHub Release URL

Changes

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 First seen · 47 lines · 12 tokens per session scan A 7b8530abaa16

Subscribe to this mod's changes

deployer is an agent published in the GitHub repository vtemian/micode (510 stars, last pushed 11d ago), licensed MIT. It adds 12 tokens to every session and 378 once invoked, about $0.0000 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-09-08.

DevOps and cloud Git and workflow Releases

deployer next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
deployervtemian/micode	Agent	510	11d ago	MIT	A	12	OpenCode
deployment-specialistluongnv89/claude-howto	Agent	47k	3d ago	MIT	A	8	Claude Code
release-validatorrlajous/claude-code-commands	Agent	30	3d ago	MIT	A	25	Claude Code
shipperngocsangyem/MeowKit	Agent	15	5d ago	MIT	A	57	Claude Code
irisils15/pantheon-legacy	Agent	12	6d ago	MIT	A	45	Claude Code
pr-ghostwriterkomunite/kalfa	Agent	246	6mo ago	MIT	A	81	Claude Code
release-executordynos-fit/dynos-work	Agent	2	4d ago	MIT	A	67	Claude Code

micode: Agent for OpenCode