hana-developer-cli-tool-example copilot-instructions.md

Project-specific instructions for the SAP HANA developer CLI example, a Node.js tool with command-line, server, and MCP modes.

In plain words
What is it for?
Use them when working in this repository, especially for its ESM code, translated user messages, documentation, architecture, and tests.
Why use it?
They give coding agents the project context, conventions, testing approach, and preferred tools needed for consistent changes.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/sap-samples/hana-developer-cli-tool-example/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/SAP-samples/hana-developer-cli-tool-example

Made for: GitHub Copilot.

Per session 625 This file is loaded in full into every session.
When invoked 625 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00625 $0.00625
Opus 5 $0.00313 $0.00313
Sonnet 5 $0.00125 $0.00125
Haiku 4.5 $0.00063 $0.00063

Measured 2d ago against content hash c47227d23e31, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

hana-developer-cli-tool-example copilot-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.

.github/copilot-instructions.md · 53 lines

How it starts

The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Workspace Copilot Instructions

These instructions apply to all work in this repository.

Project Context

For comprehensive architecture and design patterns, refer to project-overview.instructions.md. It contains:

  • Project purpose, mission, and use cases
  • Complete architecture overview with diagrams
  • Technology stack and framework details
  • Operating modes (CLI, Interactive, API Server, MCP Server)
  • Key architectural patterns (lazy loading, database abstraction, i18n, etc.)
  • Testing strategy and documentation system
  • Critical development rules and common workflows

Quick Reference:

  • Node.js ESM project ("type": "module"); prefer ESM import/export patterns.
  • CLI uses i18n; all user-facing text must go through text bundles.
  • Docs are VitePress-based; keep structure and taxonomy consistent.

General Expectations

  • Keep changes minimal and consistent with existing style.
  • Prefer updating existing utilities/scripts over introducing new ones.
  • Use repository instructions in .github/instructions/ when they match file scope.
  • Avoid modifying docs or workflows unless explicitly requested.
  • When adding scripts, keep them cross-platform.

Testing and Validation

  • Run targeted tests only when needed; do not run the full suite unless requested.
  • For docs changes, consider regenerating the docs index or building VitePress.
  • For i18n changes, validate using the existing i18n validation script.
  • For documentation creation or updates, perform a consistency-only cross-check against current sources (no command execution unless explicitly requested).

Tooling Preferences

  • Use the existing scripts in scripts/ and root automation scripts when available.
  • Avoid introducing new dependencies unless necessary and justified.

Database Operations and Inspection

  • When asked about database operations, schema inspection, or data queries, use hana-cli commands directly to inspect and interact with the database.
  • Common database inspection commands:
    • hana-cli tables - List all tables in the current schema
    • hana-cli inspectTable [schema] [table] - Show table columns and structure
    • hana-cli querySimple --query "SELECT * FROM TABLE" - Execute SQL with --query flag (supports --output json|csv|table|excel)
    • hana-cli indexes [schema] [table] - List indexes on a table
    • hana-cli dependencies [schema] [object] - Show object dependencies
  • Important: Always use the --query flag with querySimple: hana-cli querySimple --query "SQL statement" (not positional arguments)
  • Use actual database queries via hana-cli rather than relying on code inspection; this provides real, up-to-date information for testing and validation.
  • For custom SQL queries, use hana-cli querySimple to execute the SQL and get structured JSON results back, enabling programmatic analysis.
  • Document any database schema changes, new tables, or structural modifications discovered during inspection.

Read the full file on GitHub · 53 lines

Changes

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.

  1. 2d ago First seen · 53 lines · 625 tokens per session scan A c47227d23e31

Subscribe to this mod's changes

hana-developer-cli-tool-example copilot-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 625 tokens to every session, about $0.0031 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.