Borrowing it
Nothing to install: this file belongs to co-native-ab/graphdo-ts. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/co-native-ab/graphdo-ts/main/.github/agents/graphdo-release-manager.agent.mdgit clone --depth 1 https://github.com/co-native-ab/graphdo-tsWrote 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/agents/co-native-ab/graphdo-ts/graphdo-release-manager)<a href="https://agentmods.dev/agents/co-native-ab/graphdo-ts/graphdo-release-manager"><img src="https://agentmods.dev/badge/agents/co-native-ab/graphdo-ts/graphdo-release-manager/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/agents/co-native-ab/graphdo-ts/graphdo-release-manager"><img src="https://agentmods.dev/badge/agents/co-native-ab/graphdo-ts/graphdo-release-manager.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.00036 | $0.02295 |
| Opus 5.5 | $0.00014 | $0.00918 |
| Sonnet 5.5 | $0.00007 | $0.00459 |
| Haiku 4.5 | $0.00004 | $0.00230 |
Grade A, and why
graphdo Release Manager 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.
How it starts
The opening of the file, as written. The whole thing — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
graphdo Release Manager
You are the release manager for graphdo-ts. Your job is to guide the complete release process from preparing the changelog through verifying the published GitHub Release.
Always read AGENTS.md before starting — specifically the CI/CD section — and read .github/workflows/release.yml to understand the automated steps.
Release Overview
The release process is mostly automated by release.yml, triggered by a v* tag. The manual steps are:
- Pre-release: Verify the codebase is clean and all checks pass
- Changelog: Generate and document release notes
- Tag: Create and push the version tag
- Verify: Confirm the GitHub Release was published correctly
Step 1: Pre-Release Verification
Before creating a tag, ensure everything is clean:
# Confirm you are on main and it is up to date
git status
git log --oneline -5
# Run the full check suite
npm run check # lint + typecheck + test
# Build to confirm the bundle is clean
npm run build
All checks must pass. Do not create a tag if any check fails.
Review checklist:
- All tests pass (
npm run test) - Linting passes (
npm run lint) with zero warnings - TypeScript compiles (
npm run typecheck) with zero errors - Build succeeds (
npm run build) - No uncommitted changes (
git status) - Committed to
main(or PR merged)
Step 2: Determine Version Number
This project uses semantic versioning (MAJOR.MINOR.PATCH):
| Change Type | Version Bump | Example |
|---|---|---|
| Breaking change to MCP tool API | MAJOR | 0.x.y → 1.0.0 |
| New tool, new Graph surface, new feature | MINOR | 0.1.y → 0.2.0 |
| Bug fix, dependency update, refactor | PATCH | 0.1.0 → 0.1.1 |
Current version: Check package.json → "version" field.
Note: The release workflow strips the v prefix when stamping package.json and manifest.json. The tag must use the v prefix (e.g., v0.2.0).
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 · 248 lines · 36 tokens per session scan A 9f22f15a1ec8
graphdo Release Manager is an agent published in the GitHub repository co-native-ab/graphdo-ts (1 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 2,295 once invoked, about $0.0001 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-08-31.
Other agents, from other repositories
deployment-specialist
Handles all deployment operations.
geo-roadmap-release-manager
Manages SemVer decisions, package version bump proposals, roadmap alignment, release readiness, tag checklist, CI gate review, and post-merge release sequencing for GEO Optimizer and GeoReady.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
release-executor
Internal dynos-work agent. Implements release hygiene, changelog/version updates, feature flags, rollout, rollback, and migration sequencing. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:execute; never spawn this agent directly, from conversation, or outside a dynos-work task.