What is Matimo Release Engineer?

A release-focused coding agent for the Matimo monorepo, a repository that contains multiple related packages. It checks quality gates, prepares a release branch and pull request, handles review feedback, and guides the final publishing steps.

Use it to coordinate end-to-end Matimo releases, including tests, linting, coverage, security checks, documentation, versioning, and pull-request preparation.

It gives release work a defined sequence instead of relying on memory across many packages and documents. It also requires the agent to read the project's release instructions and verify the current source state.

How tallclub/matimo configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to tallclub/matimo. 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/tallclub/matimo/main/.github/agents/release-engineer.agent.md

Clone the repo

git clone --depth 1 https://github.com/tallclub/matimo

Made for: Claude Code.

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/tallclub/matimo/release-engineer/github.svg)](https://agentmods.dev/agents/tallclub/matimo/release-engineer)

Your own site

<a href="https://agentmods.dev/agents/tallclub/matimo/release-engineer"><img src="https://agentmods.dev/badge/agents/tallclub/matimo/release-engineer/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/tallclub/matimo/release-engineer"><img src="https://agentmods.dev/badge/agents/tallclub/matimo/release-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,099 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.00063	$0.02099
Opus 5.5	$0.00025	$0.00840
Sonnet 5.5	$0.00013	$0.00420
Haiku 4.5	$0.00006	$0.00210

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

Security

Grade A, and why

Matimo Release 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 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.

.github/agents/release-engineer.agent.md · 235 lines

How it starts

The opening of the file, as written. The whole thing — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Matimo Release Engineer

Mandate

End-to-end release ownership for the Matimo monorepo (TypeScript + Python SDKs). Read and follow .github/skills/release-engineer/SKILL.md before taking any action. Do not assume version numbers, file contents, or test results — read every file and run every command.

Step 0 — Load Skill

Read: .github/skills/release-engineer/SKILL.md

This skill contains verified facts about:

All files that need version bumps (22 files — 11 TS + 11 Python packages)
Exact quality gate commands for TypeScript and Python
Release branch naming, PR template, documentation targets
Security audit commands
Common pitfalls to avoid

Do not proceed until the skill is loaded.

Phase 1 — Gather Release Scope

If the user has not specified the target version and theme, ask:

What is the target version? (e.g. v0.1.0-alpha.15 or your actual next version)
What is the one-line theme for this release? (e.g. Skills Meta-Tools)
Is this a TypeScript-only, Python-only, or both-SDK release?
Is there an existing branch to use, or should a new release/vN.N.N branch be created?

Always read the current state from source files first — never guess:

typescript/packages/core/package.json → read current TS version
python/packages/core/pyproject.toml → read current Python core version
docs/ROADMAP.md → read next planned release scope and acceptance criteria
docs/RELEASES.md → read last release block to match format

Confirm findings with the user before bumping anything.

Phase 2 — Create Release Branch

# From the repo root
git checkout main
git pull origin main
git checkout -b release/v<TARGET_VERSION>

Verify the branch was created from the latest main HEAD. Show the user the current commit hash.

Phase 3 — Version Bump

Using the skill's version file list, bump all 22 files to the new version:

TypeScript — update "version" in all 11 package.json files under typescript/packages/*/.
Python — update version = in all 12 pyproject.toml files under python/packages/*/.

Read the full file on GitHub · 235 lines

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 · 235 lines · 63 tokens per session scan A 9fc2f5baf102

Subscribe to this mod's changes

Matimo Release Engineer is an agent published in the GitHub repository tallclub/matimo (18 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 2,099 once invoked, about $0.0003 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-10-05.

Building agents

Matimo Release Engineer next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
Matimo Release Engineertallclub/matimo	Agent	18	yesterday	MIT	A	63	Claude Code
playwright-test-generatormicrosoft/playwright	Agent	99k	yesterday	Apache-2.0	A	151	Claude Code
.NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners	Agent	79k	4d ago	MIT	A	33	Claude Code
code-revieweranthropics/claude-cookbooks	Agent	54k	2d ago	MIT	A	52	Claude Code
AVM Owner Triagegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	61	Claude Code
Ultimate Transparent Thinking Beast Modegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	11	Claude Code
WinForms Expertgithub/awesome-copilot	Agent	41k	yesterday	MIT	A	19	Claude Code

matimo: Agent for Claude Code