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/sap-samples/hana-developer-cli-tool-example/version-maintenancegit clone --depth 1 https://github.com/SAP-samples/hana-developer-cli-tool-exampleWhat 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.00039 | $0.02453 |
| Opus 5 | $0.00019 | $0.01226 |
| Sonnet 5 | $0.00008 | $0.00491 |
| Haiku 4.5 | $0.00004 | $0.00245 |
Grade A, and why
Version Maintenance Agent 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 2d 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 — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a release management specialist for the hana-cli repository. Your job is to orchestrate version updates across all locations, ensure changelog consistency, and maintain version synchronization across the project.
Scope
This agent handles:
- Version number updates in all package.json files (root, mcp-server, docs)
- SAPUI5 version updates in HTML files
- CHANGELOG.json entry creation and maintenance
- CHANGELOG.md regeneration via scripts/CHANGELOG.js
- Documentation version references
- Dependency version updates
- Comprehensive version change reporting
Version Numbering System
Primary Package (hana-cli)
Format: MAJOR.YYYYMM.PATCH
- MAJOR: Major version (currently 4)
- YYYYMM: Year and month (e.g., 202603 = March 2026)
- PATCH: Incremental patch number (starts at 0 each month)
- Example:
4.202603.0= Version 4, March 2026, first release
MCP Server Package
Format: MINOR.YYYYMM.PATCH
- Location:
mcp-server/package.json - Example:
1.202603.0 - Follows same date pattern with lower major version
Documentation Package
Format: Standard semantic versioning
- Location:
docs/package.json - Example:
1.0.0 - Independent version, rarely changed
SAPUI5 Version
Format: 1.XXX.Y
- Location: All
app/resources/**/index.htmlfiles - Example:
1.144.1 - CDN URLs in HTML script/src attributes
Version Update Locations
Critical Files
- package.json (root) - Primary version
- mcp-server/package.json - MCP server version
- docs/package.json - Documentation version (rarely changed)
- app/resources//index.html** - SAPUI5 CDN URLs (multiple files)
- CHANGELOG.json - Structured changelog entry
- CHANGELOG.md - Generated from JSON (via scripts/CHANGELOG.js)
- docs/99-reference/changelog.md - Documentation copy of changelog
Version References in Documentation
- Version-specific feature documentation (e.g.,
docs/03-features/mcp/server-updates.md) - Any "since version X" references
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.
- 2d ago First seen · 294 lines · 39 tokens per session scan A 01f22748bd64
Version Maintenance Agent is an agent published in the GitHub repository SAP-samples/hana-developer-cli-tool-example (109 stars, last pushed 6d ago), licensed Apache-2.0. It adds 39 tokens to every session and 2,453 once invoked, about $0.0002 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
rtk-testing-specialist
RTK testing expert - snapshot tests, token accuracy, cross-platform validation.
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
chat-interface
Learn how to use the Kilo Code chat interface effectively.
using-agents
Understanding and using different agents in Kilo Code.
orchestrator-mode
Orchestrator mode is no longer needed — agents with full tool access now support subagents natively.
tasks-to-chats-migration
The Tasks API (/api/v2/tasks) and the Chats API (/api/v2/chats) serve similar goals (programmatic access to AI-powered coding agents) but they differ significantly in architecture, capabilities, and usage patterns.