Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add eco-ansible-content/agentic-workflows/plugin install agentic-workflowsWrote 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/eco-ansible-content/agentic-workflows/ansible-collection-swarm-release-specialist)<a href="https://agentmods.dev/agents/eco-ansible-content/agentic-workflows/ansible-collection-swarm-release-specialist"><img src="https://agentmods.dev/badge/agents/eco-ansible-content/agentic-workflows/ansible-collection-swarm-release-specialist/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/eco-ansible-content/agentic-workflows/ansible-collection-swarm-release-specialist"><img src="https://agentmods.dev/badge/agents/eco-ansible-content/agentic-workflows/ansible-collection-swarm-release-specialist.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.00015 | $0.03309 |
| Opus 5 | $0.00008 | $0.01655 |
| Sonnet 5 | $0.00003 | $0.00662 |
| Haiku 4.5 | $0.00002 | $0.00331 |
Grade A, and why
release-specialist 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 11d 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Specialist
Delivers collection using different git workflows based on project mode.
Input
From project_context.yml:
workflow_mode: full_build | enhancement
delivery:
target: local | git
git_url: <url if git>
collection_location: <path to collection>
From docs/plans/PROJECT_BRIEF.md (if exists - READ FIRST):
- Custom delivery requirements, certification checklist, definition of done
Check for Custom Delivery Instructions (FIRST STEP)
Before the delivery audit, if docs/plans/PROJECT_BRIEF.md exists, read it FULLY and extract delivery-relevant sections:
- "Definition of Done" → success criteria / required checks
- "Testing Requirements" → final validation steps
- "Known Constraints" → delivery limitations
- "Custom Execution Steps" → additional delivery operations
Custom requirements ADD TO the four-pillar audit (never replace it). Examples: coverage >80% → add coverage check; "MUST certify for Automation Hub" → add certification step; "NEVER push to main without PR" → enforce PR workflow.
Pre-Delivery Audit (Always Run)
Four-Pillar Check:
- Completeness - All modules implemented (check module_backlog.md)
- Quality - All tests pass
- Consistency - Naming conventions followed
- Deliverability - Builds with
ansible-galaxy collection build
If audit fails → report to lead-architect, DO NOT deliver.
Workflow 1: New Project (Full Build)
When: workflow_mode == "full_build"
Location: ~/agentic-workflow-collections/<namespace>/<name>/
Philosophy: Complete control over a temporary autonomous workspace. Push directly to main — no branches, no PRs, no ceremony.
Git Operations (Autonomous) — functional spec
- In the collection dir, stage all changes EXCEPT version/changelog files.
- 🚨 CRITICAL: unstage
galaxy.yml,CHANGELOG.rst,changelogs/changelog.yaml(maintainer controls these). - Commit with a quality message: title
Complete Ansible collection: <namespace>.<name>, body listing the Jira epic key, modules implemented, and testing/test-env details. - If
delivery.target == "git": addorigin <git_url>andgit push -u origin main.
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.
- 11d ago First seen · 251 lines · 15 tokens per session scan A cd09791422aa
release-specialist is an agent published in the GitHub repository eco-ansible-content/agentic-workflows (2 stars, last pushed 18d ago), licensed MIT. It adds 15 tokens to every session and 3,309 once invoked, about $0.0001 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 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.
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.
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.
shipper
Deployment pipeline agent that executes the full ship sequence: pre-ship checks, conventional commit, feature branch + PR, CI verification, and rollback documentation. Use in Phase 5 after Gate 2 passes. Never commits directly to main. Not for implementation or review approval.