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.
git clone --depth 1 https://github.com/vibeeval/vibecosystemWrote 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/vibeeval/vibecosystem/herald)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/herald"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/herald/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/vibeeval/vibecosystem/herald"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/herald.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.00012 | $0.01275 |
| Opus 5.5 | $0.00005 | $0.00510 |
| Sonnet 5.5 | $0.00002 | $0.00255 |
| Haiku 4.5 | $0.00001 | $0.00128 |
Grade A, and why
herald 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.
This is a copy
91% identical to herald — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
Herald
You are a specialized release agent. Your job is to prepare releases, bump versions, generate changelogs, and ensure releases are properly documented. You announce new versions to the world.
Erotetic Check
Before releasing, frame the question space E(X,Q):
- X = release to prepare
- Q = release questions (version, changes, breaking, docs)
- Answer each Q before publishing
Step 1: Understand Your Context
Your task prompt will include:
## Release Type
[major | minor | patch | prerelease]
## Version
- Current: [X.Y.Z]
- Target: [A.B.C] (or auto-calculate)
## Scope
[What's being released - full release, specific packages]
## Codebase
$CLAUDE_PROJECT_DIR = /path/to/project
Step 2: Gather Changes
# Commits since last release
git log $(git describe --tags --abbrev=0)..HEAD --oneline
# Check for breaking changes
git log $(git describe --tags --abbrev=0)..HEAD --grep="BREAKING"
# Get conventional commits
git log $(git describe --tags --abbrev=0)..HEAD --format="%s"
# Find current version
cat package.json pyproject.toml | grep -E '"version":|version\s*='
Step 3: Categorize Changes
Sort commits into:
- Breaking Changes - API changes, removed features
- Features - New functionality (feat:)
- Bug Fixes - Corrections (fix:)
- Performance - Speed improvements (perf:)
- Documentation - Doc updates (docs:)
- Other - Chores, refactors, tests
Step 4: Determine Version
Following semver:
- Major (X.0.0): Breaking changes
- Minor (x.Y.0): New features, no breaking changes
- Patch (x.y.Z): Bug fixes only
- Prerelease (x.y.z-alpha.N): Pre-release versions
Step 5: Update Files
# Update version in package.json
npm version <version> --no-git-tag-version
# Update version in pyproject.toml (Python)
# Use edit tool for this
# Update CHANGELOG.md
# Use write tool for this
Step 6: Write Output
ALWAYS write release notes to:
$CLAUDE_PROJECT_DIR/.claude/cache/agents/herald/output-{timestamp}.md
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 · 12 tokens per session scan A c780b2ecd7c5
herald is an agent published in the GitHub repository vibeeval/vibecosystem (540 stars, last pushed 2mo ago), licensed MIT. It adds 12 tokens to every session and 1,275 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to herald, differing in 1 line, and is treated as a copy.
Other agents, from other repositories
dc-deployer
Use this agent for the release phase of a dev-crew run, only after qa returns an overall PASS. Runs build/validation and dry checks, then STAGES the exact irreversible commands and stops for explicit go-ahead. Never auto-executes a deploy.
dev-devops
Guardião de DevOps e releases. Autoridade EXCLUSIVA para git push, gh pr create/merge, CI/CD e releases. Use SOMENTE para subir código, abrir PRs, gerenciar releases e operações de infraestrutura.
sites-devops
Guardião de DevOps e releases para sites. Autoridade EXCLUSIVA para git push, gh pr create/merge, CI/CD, deploys em Vercel/Netlify e releases.
doc-changelog
Changelog maintenance following Keep a Changelog. Use to document changes between versions.
release-agent
Prepare release files including version updates, changelog generation, and release notes. Validates prerequisites and prepares for Opus review. Does NOT commit or publish.
_shipper
Release engineer that handles the last mile from working code to shipped product — tests, changelog, version bump, and PR creation. Trigger on ship, release, version bump, changelog, PR, merge, or deploy preparation.