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.
npx agentmods add instructions/sap-samples/hana-developer-cli-tool-example/general-documentationgit clone --depth 1 https://github.com/SAP-samples/hana-developer-cli-tool-exampleWhat 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 | $0.01105 | $0.01105 |
| Opus 5 | $0.00553 | $0.00553 |
| Sonnet 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 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.
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.
- 2d 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 (109 stars, last pushed 7d ago), licensed Apache-2.0. It adds 1,105 tokens to every session, about $0.0055 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.
Other instructions, from other repositories
rtk CLAUDE.md
Claude Code instructions for rtk-ai/rtk, covering claude.md, project overview, name collision warning, development commands and build & run.
rtk copilot-instructions.md
Copilot instructions for rtk-ai/rtk, covering copilot instructions for rtk, using rtk in this session, instead of: use, build, test & lint and pre-commit gate (must all pass before any pr).
awesome-vscode CLAUDE.md
Instructions for viatsko/awesome-vscode, covering claude.md, what this repo is, adding an entry, themes and linting / ci.
vscode-peacock AGENTS.md
Instructions for johnpapa/vscode-peacock, covering peacock — agent guide, project overview, repository structure, tech stack and build & run.
cs CLAUDE.md
Instructions for boyter/cs, covering claude.md, project overview, build & test commands, architecture and query pipeline (pkg/search/).
docs-mcp-server AGENTS.md
Instructions for arabold/docs-mcp-server, covering agent instructions for docs-mcp-server, repository context, development workflow, key commands and git workflow.