Continuous-Claude-v3 is a Claude Code development environment that preserves working context between sessions, coordinates specialized agents, and stores project knowledge through ledgers, handoffs, and analysis tools. It is for people using Claude Code on ongoing or complex software work. Its catalogue entries are the skills, agents, hooks, plugin, and setting that provide its workflows and orchestration.
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/parcadei/continuous-claude-v3/heraldgit clone --depth 1 https://github.com/parcadei/Continuous-Claude-v3Wrote 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/parcadei/continuous-claude-v3/herald)<a href="https://agentmods.dev/agents/parcadei/continuous-claude-v3/herald"><img src="https://agentmods.dev/badge/agents/parcadei/continuous-claude-v3/herald.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.1 | $0.00012 | $0.01269 |
| Opus 5 | $0.00006 | $0.00634 |
| Sonnet 5 | $0.00002 | $0.00254 |
| Haiku 4.5 | $0.00001 | $0.00127 |
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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- herald — 91% identical, 1 lines differ
How it starts
The opening of the file, as written. The whole thing — 234 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.
- 6d ago First seen · 234 lines · 12 tokens per session scan A 2281b058847a
herald is an agent published in the GitHub repository parcadei/Continuous-Claude-v3 (3,936 stars, last pushed 7mo ago), licensed MIT. It adds 12 tokens to every session and 1,269 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-30.
Other agents, from other repositories
fizzy-tasks
Lightweight agent for Fizzy.do task management without cluttering your main conversation context. Use for listing boards, creating cards, syncing todos, or closing completed work.
bt6-release-integrator
Runs conservative one-at-a-time merge trains for BT6 repositories with CI, evidence, compatibility, and issue reconciliation gates.
release-bot
Prepares releases — changelog, version bump, tag checklist.
e2e-test-agent
E2E test agent for validation.
git-flow
Оркестрирует полный цикл изменений в git: создание ветки → атомарные коммиты по Conventional Commits → описание PR → merge → semver-тег (если релиз). Вызывает скиллы git-conventional-commit, git-pr-description, git-release-tag. Используй, когда задача — провести изменение через git от ветки до релиза или хотя бы до PR.
release
Cut a release of the cli package: bump the version, tag, and publish.