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/copilot-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/copilot-instructions)<a href="https://agentmods.dev/instructions/sap-samples/hana-developer-cli-tool-example/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/copilot-instructions/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/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/copilot-instructions.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.00625 | $0.00625 |
| Opus 5.5 | $0.00250 | $0.00250 |
| Sonnet 5.5 | $0.00125 | $0.00125 |
| Haiku 4.5 | $0.00063 | $0.00063 |
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 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 — 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-clicommands directly to inspect and interact with the database. - Common database inspection commands:
hana-cli tables- List all tables in the current schemahana-cli inspectTable [schema] [table]- Show table columns and structurehana-cli querySimple --query "SELECT * FROM TABLE"- Execute SQL with--queryflag (supports--output json|csv|table|excel)hana-cli indexes [schema] [table]- List indexes on a tablehana-cli dependencies [schema] [object]- Show object dependencies
- Important: Always use the
--queryflag with querySimple:hana-cli querySimple --query "SQL statement"(not positional arguments) - Use actual database queries via
hana-clirather than relying on code inspection; this provides real, up-to-date information for testing and validation. - For custom SQL queries, use
hana-cli querySimpleto 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.
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 · 53 lines · 625 tokens per session scan A c47227d23e31
hana-developer-cli-tool-example copilot-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 625 tokens to every session, about $0.0025 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.