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/project-overviewgit 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.09441 | $0.09441 |
| Opus 5 | $0.04720 | $0.04720 |
| Sonnet 5 | $0.01888 | $0.01888 |
| Haiku 4.5 | $0.00944 | $0.00944 |
Grade A, and why
hana-developer-cli-tool-example project-overview.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 — 1,263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAP HANA Developer CLI Tool - Project Overview
This document provides comprehensive context about the project's purpose, architecture, and design patterns. Reference this before making significant changes or when onboarding to the codebase.
Project Purpose and Mission
The SAP HANA Developer CLI Tool is a comprehensive, developer-centric command-line interface designed to simplify SAP HANA database operations during local and cloud-based development.
Core Objectives:
- Provide 100+ database commands across 16 functional categories
- Simplify complex multi-step database operations into single commands
- Support multiple operating modes (CLI, Interactive, API Server, MCP Server)
- Work seamlessly in both local and cloud development environments
- Integrate with modern development toolchains (VS Code, SAP Business Application Studio, Cloud Shells)
Target Use Cases:
- Local SAP HANA development (SAP HANA Express Edition, Remote HANA)
- Cloud-based development (SAP BTP, HANA Cloud, Google Cloud Shell, AWS Cloud9)
- Database administration and maintenance
- Data analysis, profiling, and validation
- Schema management and migration
- Performance monitoring and optimization
Not Intended For:
- Replacing hdbsql as a generic SQL console
- Production database administration (primarily a development tool)
Project Architecture
High-Level Architecture Diagram
┌─────────────────────────────────────────────────────────────────┐
│ SAP HANA Developer CLI │
├─────────────────────────────────────────────────────────────────┤
│ │
│ ┌───────────┐ ┌──────────┐ ┌──────────┐ ┌──────────────┐ │
│ │ CLI Mode │ │Interactive│ │API Server│ │ MCP Server │ │
│ │ (yargs) │ │ Mode │ │ (Express)│ │(TypeScript) │ │
│ └─────┬─────┘ └─────┬────┘ └─────┬────┘ └──────┬───────┘ │
│ │ │ │ │ │
│ └──────────────┴──────────────┴───────────────┘ │
│ │ │
│ ┌───────▼────────┐ │
│ │ Command Layer │ │
│ │ (bin/*) │ │
│ └───────┬────────┘ │
│ │ │
│ ┌───────────────────┼───────────────────┐ │
│ │ │ │ │
│ ┌─────▼─────┐ ┌────────▼────────┐ ┌────▼────┐ │
│ │ Utils │ │ DB Abstraction │ │ Routes │ │
│ │ (base.js, │ │ Layer (CDS/ │ │(Express)│ │
│ │connections)│ │ native clients) │ │ │ │
│ └───────────┘ └─────────┬────────┘ └─────────┘ │
│ │ │
│ ┌───────────────┼───────────────┐ │
│ │ │ │ │
│ ┌──────▼──────┐ ┌──────▼──────┐ ┌─────▼──────┐ │
│ │ HANA │ │ PostgreSQL │ │ SQLite │ │
│ │ (Direct/CDS)│ │ (CDS) │ │ (CDS) │ │
│ └─────────────┘ └─────────────┘ └────────────┘ │
│ │
└─────────────────────────────────────────────────────────────────┘
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 · 1,263 lines · 9,441 tokens per session scan A 51da257f6b0b
hana-developer-cli-tool-example project-overview.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 9,441 tokens to every session, about $0.0472 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
kilocode AGENTS.md
AGENTS.md instructions for Kilo-Org/kilocode, covering agents.md, build and dev, quality checks, products and package instructions.
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/).
language-tools AGENTS.md
Instructions for prisma/language-tools, covering agent guide for prisma language tools, project overview, packages, documentation and quick start.
getspecstory copilot-instructions.md
Instructions for specstoryai/getspecstory: Examine the file changes for the pull request.
vscode-gitlens AGENTS.md
AGENTS.md instructions for gitkraken/vscode-gitlens, covering gitlens development guide, working style expectations, development environment, development commands and git & repository guidelines.