Borrowing it
Nothing to install: this file belongs to SAP-samples/hana-developer-cli-tool-example. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/SAP-samples/hana-developer-cli-tool-example/main/.github/instructions/route-development.instructions.mdgit clone --depth 1 https://github.com/SAP-samples/hana-developer-cli-tool-exampleWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/sap-samples/hana-developer-cli-tool-example/route-development)<a href="https://agentmods.dev/instructions/sap-samples/hana-developer-cli-tool-example/route-development"><img src="https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/route-development/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/sap-samples/hana-developer-cli-tool-example/route-development"><img src="https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/route-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.05092 | $0.05092 |
| Opus 5.5 | $0.02037 | $0.02037 |
| Sonnet 5.5 | $0.01018 | $0.01018 |
| Haiku 4.5 | $0.00509 | $0.00509 |
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 1mo 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 — 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
- Consistency: All routes follow the same structural pattern and registration method.
- Error Handling: Errors propagate to centralized Express error middleware, never handled inline.
- Connection Management: Database connections are cleared before use and created as needed.
- Internationalization: All user-facing strings come from i18n bundles via
base.bundle.getText(key). - Response Standardization: Use
base.sendResults(res, results)for consistent JSON response formatting. - Swagger Documentation: Every endpoint includes JSDoc comments for auto-generated API docs.
- CLI Integration: Dynamic imports enable newly added CLI commands to be instantly available to routes.
- 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)
}
})
}
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.
- 1mo ago First seen · 740 lines · 5,092 tokens per session scan A c54047908df4
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 (114 stars, last pushed 11d ago), licensed Apache-2.0. It adds 5,092 tokens to every session, about $0.0204 per session on Opus 5.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
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.