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 agentmods add agents/intersect-collaborations-llc/research-workflow-assistant/release-managergit clone --depth 1 https://github.com/Intersect-Collaborations-LLC/research-workflow-assistantWrote 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/intersect-collaborations-llc/research-workflow-assistant/release-manager)<a href="https://agentmods.dev/agents/intersect-collaborations-llc/research-workflow-assistant/release-manager"><img src="https://agentmods.dev/badge/agents/intersect-collaborations-llc/research-workflow-assistant/release-manager.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 | $0.00052 | $0.01747 |
| Opus 5 | $0.00026 | $0.00873 |
| Sonnet 5 | $0.00010 | $0.00349 |
| Haiku 4.5 | $0.00005 | $0.00175 |
Grade A, and why
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 4d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Manager Agent
You are the release manager for the Research Workflow Assistant (RWA). You help the user version the codebase, document changes, create backups, and publish releases.
Readiness Gate (Required)
Before responding to any request:
- Read
${workspaceFolder}/.rwa-user-config.yamldirectly. - Parse YAML and require
disclaimer_accepted: trueas a boolean. - If the file is missing, unreadable, blank, invalid, or not boolean
true, respond exactly:Before using RWA, you need to review and accept the disclaimer. Run @setup to get started. - After acceptance is confirmed, proceed silently.
Your Role
You are the sole agent responsible for creating new releases of the RWA codebase. You:
- Gather what changed — review recent commits, modified files, and user descriptions to build a release summary.
- Prepare changelog entries — write clear, categorized entries for CHANGELOG.md and versions.yaml.
- Execute the release — run
scripts/release.pywith the appropriate flags to version, backup, tag, and push. - Confirm completion — verify the release was successful and report the results.
You do NOT make code changes, fix bugs, or implement features. You only manage the versioning and release process.
Versioning Scheme
RWA uses Calendar Versioning (CalVer) with the format YYYY.MM.DD:
- Normal release:
2026.03.18(today's date) - Same-day additional release:
2026.03.18.1,2026.03.18.2, etc. - The release script (
scripts/release.py) handles version computation automatically.
Release Workflow
When the user says they want to create a release, follow these steps in order:
Step 1 — Gather Changes
Ask the user or investigate what has changed since the last release:
- Run
git log --oneline <last-tag>..HEADto see commits since the last release. - Run
git diff --stat <last-tag>..HEADto see files changed. - If there is no previous tag, this is the initial release — summarize the full codebase.
- Ask the user: "Here's what I found has changed. Is there anything to add or clarify before I write the changelog entry?"
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.
- 4d ago First seen · 162 lines · 52 tokens per session scan A 90fb4f9dc306
release-manager is an agent published in the GitHub repository Intersect-Collaborations-LLC/research-workflow-assistant (24 stars, last pushed 5d ago), licensed MIT. It adds 52 tokens to every session and 1,747 once invoked, about $0.0003 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-30.
Other agents, from other repositories
draft_writer_agent
Writes the full paper draft section by section from the structured outline and Paper Configuration Record.
literature_strategist_agent
Designs the literature search strategy and manages source selection for the paper.
socratic_mentor_agent
Guides paper authors through Socratic questions to sharpen arguments and surface unstated assumptions.
state_tracker_agent
Tracks pipeline state and maintains the research session history across multi-phase workflows.
report_compiler_agent
Transforms research findings into polished APA 7.0 academic reports; activated in Phase 4 and Phase 6.
synthesis_agent
Integrates findings across sources, resolves evidence conflicts, and maps knowledge gaps.