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/nxtg-ai/forge-plugin/release-sentinelgit clone --depth 1 https://github.com/nxtg-ai/forge-pluginWhat 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.00000 | $0.01482 |
| Opus 5 | $0.00000 | $0.00741 |
| Sonnet 5 | $0.00000 | $0.00296 |
| Haiku 4.5 | $0.00000 | $0.00148 |
Grade A, and why
release-sentinel 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 3d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Sentinel
Your documentation never drifts from your code again -- the agent that audits, maps, and auto-updates docs whenever your codebase changes.
| Level | L1 Vibe Coder |
| Category | Governance & Analysis |
| Model | Opus |
What It Does
The Release Sentinel is a documentation management specialist that maintains synchronization between your code and your docs. It knows that stale documentation erodes trust faster than missing documentation -- a wrong answer is worse than no answer.
It works by maintaining a mapping between code patterns and documentation files. When your API endpoints change, it identifies which docs pages are affected. When you add a new CLI command, it flags the reference page that needs updating. When you ship a release, it compiles conventional commits into a human-readable changelog. The result is documentation that stays current without requiring a dedicated docs sprint every quarter.
The agent classifies documentation updates into three tiers: auto-updated (changelogs, API reference, type definitions), semi-auto (README sections, user guides, FAQ entries that need human review), and manual (architecture docs, concept explanations, diagrams). This tiered approach means the mechanical work is handled automatically while human judgment is preserved for content that requires it.
When to Use It
- Post-merge documentation sync: After merging a PR that adds or modifies API endpoints, components, CLI commands, or configuration schemas.
- Pre-release documentation audit: Before cutting a release, to ensure all documentation reflects the current state of the codebase.
- Documentation health check: When you want a coverage score -- how much of your codebase has corresponding, up-to-date documentation.
- Changelog generation: When you need to compile conventional commits into a formatted, user-readable changelog for a new release.
- Refactor aftermath: After a significant refactoring that changed component interfaces, to identify which docs pages are now stale.
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.
- 3d ago First seen · 124 lines · 0 tokens per session scan A 16a765313e98
release-sentinel is an agent published in the GitHub repository nxtg-ai/forge-plugin (5 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,482 tokens. 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
code-reviewer
Reviews code for project guideline compliance, bugs, and quality issues. Use after writing code, before commits, or before PRs. Specify files to review or defaults to unstaged git changes. High-confidence issues only (80+) to minimize noise.
docs-impact
Reviews documentation affected by code changes. Identifies stale docs, removed feature references, and missing entries for new user-facing features. Reports findings with specific fixes. Advisory only - does not modify files.
scout
MUST be used for exploratory codebase research, rapid code analysis, and broad pattern searches. Fast read-only scout returning compressed context for handoff.
claude-design-orchestrator
Parses claude.ai/design handoff bundles: validates schema, dedups proposed components against the codebase via component-search, reconciles tokens, and tracks bundle→PR provenance so design intent stays linked to shipped code.
database-engineer
PostgreSQL specialist: schema design, migrations, query optimization, pgvector/full-text search, Alembic migrations.
demo-producer
Universal demo video producer that creates polished marketing videos for any content - skills, agents, plugins, tutorials, CLI tools, or code walkthroughs. Uses VHS terminal recording and Remotion composition.