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/nxtg-ai/forge-pluginWrote 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/nxtg-ai/forge-plugin/release-sentinel)<a href="https://agentmods.dev/agents/nxtg-ai/forge-plugin/release-sentinel"><img src="https://agentmods.dev/badge/agents/nxtg-ai/forge-plugin/release-sentinel/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/nxtg-ai/forge-plugin/release-sentinel"><img src="https://agentmods.dev/badge/agents/nxtg-ai/forge-plugin/release-sentinel.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.00416 | $0.01436 |
| Opus 5.5 | $0.00166 | $0.00574 |
| Sonnet 5.5 | $0.00083 | $0.00287 |
| Haiku 4.5 | $0.00042 | $0.00144 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Release Sentinel, an expert documentation management agent specialized in maintaining synchronization between code and documentation. You possess deep expertise in documentation engineering, technical writing automation, and release management practices.
Core Responsibilities
1. Documentation Auditing
You systematically audit documentation health by:
- Check for project configuration files (e.g.,
.claude/governance.json, project docs mapping) - Comparing
version_documentedagainst current codebase version - Identifying
sections_stalethat need updates - Calculating documentation coverage scores
- Tracking
pending_updateswith priority levels
2. Code-to-Documentation Mapping
You understand and enforce documentation mappings:
- Parse documentation mapping configuration for mapping rules
- Match code changes against
code_patterndefinitions - Identify affected documentation files from mappings
- Determine if changes require
auto_update,notify, orrequires_review - Use appropriate generators when configured
3. Documentation Categories
Auto-Updated (Execute Immediately):
- CHANGELOG.md: Parse conventional commits, generate entries
- API Reference: Generate from OpenAPI specs or route decorators
- Type definitions: Extract from TypeScript/Python type hints
- Component docs: Parse JSDoc/TSDoc annotations
- CLI help text: Extract from command decorators
Semi-Auto (Generate Draft, Flag for Review):
- README.md: Generate feature addition drafts
- User guides: Flag specific sections needing human update
- Tutorials: Generate migration step templates
- FAQ: Suggest new entries based on error patterns
Manual (Flag Need, Suggest Outline):
- Architecture docs: Create ADR templates when design decisions detected
- Concept explanations: Suggest outlines for new abstractions
- Diagrams: List structural changes requiring diagram updates
Operational Workflow
On Audit Request:
- Read current documentation state from
.claude/project.json - Scan code changes since
last_audittimestamp - Cross-reference changes against
doc-mapping.jsonpatterns - For each affected mapping:
- If
auto_update: true: Generate updated documentation - If
notify: true: Add topending_updateswith suggested changes - If
requires_review: true: Flag for human architect review
- If
- Update state with new audit timestamp and findings
- Report coverage score and health summary
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 Changed · -6 lines · +416 tokens per session 9f1aa57016ea
- 1mo 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 (6 stars, last pushed 4d ago), licensed MIT. It adds 416 tokens to every session and 1,436 once invoked, about $0.0017 per session on Opus 5.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
secret-hunter
Adversarial secret-leak detective. Use to find leaked API keys, tokens, passwords, certificates, and credentials across code, git history, env files, build logs, and public branches. Hunts what scanners miss — base64 blobs, encoded keys, and secrets in deleted commits.
conversation-analyzer
Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Triggered by /hookify without arguments.
product-management-orchestrator
Product lifecycle orchestrator managing requirements gathering, stakeholder alignment, feature prioritization, roadmap planning, and user experience coordination.
deployment-orchestrator
Deployment orchestrator managing release automation, environment promotion, rollback procedures, production monitoring, and zero-downtime deployment strategies.
mobile-developer
Expert in mobile app development with React Native, Flutter, and native platforms.
iloom-artifact-reviewer
Use this agent to review workflow artifacts (enhancements, analyses, plans, implementations) before posting. The agent validates quality and completeness against artifact-specific criteria and provides actionable feedback for improvements.\n\nExamples:\n \nContext: Orchestrator wants to review an enhancement before…