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 instructions/sap-samples/hana-developer-cli-tool-example/release-managementgit 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.04146 | $0.04146 |
| Opus 5 | $0.02073 | $0.02073 |
| Sonnet 5 | $0.00829 | $0.00829 |
| Haiku 4.5 | $0.00415 | $0.00415 |
Grade A, and why
hana-developer-cli-tool-example release-management.instructions.md 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 — 674 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Management Guidelines
Use this guide when preparing releases, updating the changelog, or publishing new versions of the hana-cli tool.
Scope and Purpose
This guide applies to:
- CHANGELOG.json - Structured changelog entries
- package.json - Version number updates
- scripts/CHANGELOG.js - Changelog generation script
- Release preparation and npm publishing process
Version Numbering Convention
Primary Package (hana-cli)
Format: MAJOR.YYYYMM.PATCH
Examples:
4.202602.0- Version 4, released February 2026, patch 03.202601.0- Version 3, released January 2026, patch 03.202511.0- Version 3, released November 2025, patch 0
Components:
- MAJOR - Major version number (incremented for breaking changes or significant milestones)
- YYYYMM - Year and month of release (e.g., 202602 = February 2026)
- PATCH - Patch number within the month (typically 0 for first release, 1+ for hotfixes)
MCP Server Package
Format: MINOR.YYYYMM.PATCH
Example: 1.202602.0
Location: mcp-server/package.json
Note: MCP server versioning follows same date-based pattern but with lower major version number since it's a newer component.
Documentation Package
Format: Standard semantic versioning MAJOR.MINOR.PATCH
Example: 1.0.0
Location: docs/package.json
Note: Documentation version is independent and follows standard semver.
CHANGELOG.json Structure
File Format
Location: Root directory CHANGELOG.json
Structure: Array of release objects
[
{
"date": "YYYY-MM-DD",
"version": "MAJOR.YYYYMM.PATCH",
"Changed": [
"Description of change 1",
"Description of change 2",
"..."
]
},
{
"date": "YYYY-MM-DD",
"version": "MAJOR.YYYYMM.PATCH",
"Added": [
"New feature 1",
"New feature 2"
],
"Fixed": [
"Bug fix 1"
],
"Changed": [
"Changes 1"
],
"Deprecated": [
"Deprecated item"
],
"Removed": [
"Removed feature"
],
"Security": [
"Security fix"
]
}
]
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 · 674 lines · 4,146 tokens per session scan A 60673f2aadac
hana-developer-cli-tool-example release-management.instructions.md is an instructions file published in the GitHub repository SAP-samples/hana-developer-cli-tool-example (109 stars, last pushed 7d ago), licensed Apache-2.0. It adds 4,146 tokens to every session, about $0.0207 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 instructions, from other repositories
rtk CLAUDE.md
Claude Code instructions for rtk-ai/rtk, covering claude.md, project overview, name collision warning, development commands and build & run.
rtk copilot-instructions.md
Copilot instructions for rtk-ai/rtk, covering copilot instructions for rtk, using rtk in this session, instead of: use, build, test & lint and pre-commit gate (must all pass before any pr).
awesome-vscode CLAUDE.md
Instructions for viatsko/awesome-vscode, covering claude.md, what this repo is, adding an entry, themes and linting / ci.
vscode-peacock AGENTS.md
Instructions for johnpapa/vscode-peacock, covering peacock — agent guide, project overview, repository structure, tech stack and build & run.
cs CLAUDE.md
Instructions for boyter/cs, covering claude.md, project overview, build & test commands, architecture and query pipeline (pkg/search/).
docs-mcp-server AGENTS.md
Instructions for arabold/docs-mcp-server, covering agent instructions for docs-mcp-server, repository context, development workflow, key commands and git workflow.