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/general-documentation.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/general-documentation)<a href="https://agentmods.dev/instructions/sap-samples/hana-developer-cli-tool-example/general-documentation"><img src="https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/general-documentation/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/general-documentation"><img src="https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/general-documentation.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.01105 | $0.01105 |
| Opus 5.5 | $0.00442 | $0.00442 |
| Sonnet 5.5 | $0.00221 | $0.00221 |
| Haiku 4.5 | $0.00111 | $0.00111 |
Grade A, and why
hana-developer-cli-tool-example general-documentation.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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
General Documentation Guidelines (Non-Command Docs)
Use this guide for standard documentation pages in docs/ outside docs/02-commands/.
Scope
This file applies to:
docs/01-getting-started/**/*.mddocs/03-features/**/*.mddocs/04-api-reference/**/*.mddocs/05-development/**/*.mddocs/99-reference/**/*.mddocs/troubleshooting/**/*.md- root docs pages like
docs/index.md
This file does not apply to command reference pages in docs/02-commands/** (handled by command-documentation.instructions.md).
Preservation Rule (Do Not Remove Existing Helpful Context)
When updating existing pages, preserve useful educational and explanatory content unless it is clearly outdated, incorrect, duplicated, or the user explicitly asks to remove it.
Practical rules:
- Update the target section without stripping unrelated narrative value.
- Keep existing examples if still valid; improve rather than delete.
- Maintain page-specific details (platform notes, edge cases, caveats) unless they are wrong.
Standard Page Structure
Use this baseline structure unless a page type needs a variation:
#Title (single H1)- Short intro paragraph (what this page helps with)
- Main sections with
##headings - Concrete examples (
bash,json,text, etc.) - Optional reference tables for options, comparisons, or troubleshooting mappings
## See Alsowith related internal links
Typical Section Patterns
Use patterns already common in this repo:
- Guide pages: Prerequisites → Steps/Methods → Validation → Troubleshooting → Next Steps
- Feature pages: Overview → Use Cases → Configuration → Examples → Related Topics
- API pages: Overview → Endpoints/Contracts → Request/Response examples → Error handling → Security notes
- Troubleshooting pages: Problem/Error → Likely causes → Step-by-step fixes → Verification
- Index/landing pages: Section overview + concise link lists to child pages
Writing Style
- Be concise, actionable, and user-focused.
- Prefer direct instructions over vague statements.
- Use consistent terminology: "HANA CLI", "hana-cli", "SAP HANA", "MCP".
- Avoid hype language; prioritize technical clarity.
- Keep headings descriptive and scannable.
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 · 126 lines · 1,105 tokens per session scan A 706fdebfabc7
hana-developer-cli-tool-example general-documentation.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 1,105 tokens to every session, about $0.0044 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.