hana-developer-cli-tool-example route-development.instructions.md

A set of rules for creating and updating Express route files, which define the web addresses and handlers that an application exposes.

In plain words
What is it for?
Use it when adding or changing API routes, user-interface route variants, or route registration in the SAP HANA Developer CLI Tool.
Why use it?
It keeps endpoints consistent in their errors, database connections, translations, responses, documentation, and CLI integration.

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/route-development
Clone the repo
git clone --depth 1 https://github.com/SAP-samples/hana-developer-cli-tool-example

Made for: GitHub Copilot.

Per session 5,092 This file is loaded in full into every session.
When invoked 5,092 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.05092 $0.05092
Opus 5 $0.02546 $0.02546
Sonnet 5 $0.01018 $0.01018
Haiku 4.5 $0.00509 $0.00509

Measured 2d ago against content hash c54047908df4, 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 route-development.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/instructions/route-development.instructions.md · 740 lines

How it starts

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

Route Development Guidelines

Use this guide when creating or modifying route files in the routes/ directory.

Scope and Purpose

This guide applies to all route files in routes/. Each file exports a route(app, server) function that registers one or more related endpoints on the Express application. Routes serve as bridges between HTTP clients and CLI commands.

Critical Principles

  1. Consistency: All routes follow the same structural pattern and registration method.
  2. Error Handling: Errors propagate to centralized Express error middleware, never handled inline.
  3. Connection Management: Database connections are cleared before use and created as needed.
  4. Internationalization: All user-facing strings come from i18n bundles via base.bundle.getText(key).
  5. Response Standardization: Use base.sendResults(res, results) for consistent JSON response formatting.
  6. Swagger Documentation: Every endpoint includes JSDoc comments for auto-generated API docs.
  7. CLI Integration: Dynamic imports enable newly added CLI commands to be instantly available to routes.
  8. Dual Support: When applicable, support both API (/path) and UI (/path-ui) endpoint variants.

File Structure Template

Every route file must follow this structure:

/**
 * @fileoverview [Brief description of what these routes handle]
 * 
 * Routes:
 *  - GET /path1 - [Description]
 *  - GET /path2 - [Description]
 * 
 * Dependencies: CLI commands at bin/[commandName].js, utils/base.js
 */

export async function route(app, server) {
  const base = await import('../utils/base.js')
  
  /**
   * @swagger
   * /path1:
   *   get:
   *     tags:
   *       - Category Name
   *     summary: Brief endpoint description
   *     description: Detailed endpoint description from i18n
   *     responses:
   *       200:
   *         description: Success response
   */
  app.get('/path1', async (req, res, next) => {
    try {
      // Endpoint logic
      res.status(200).json(result)
    } catch (error) {
      next(error)
    }
  })
}

Read the full file on GitHub · 740 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 · 740 lines · 5,092 tokens per session scan A c54047908df4

Subscribe to this mod's changes

hana-developer-cli-tool-example route-development.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 5,092 tokens to every session, about $0.0255 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.