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/i18n-translation-management.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/i18n-translation-management)<a href="https://agentmods.dev/instructions/sap-samples/hana-developer-cli-tool-example/i18n-translation-management"><img src="https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/i18n-translation-management/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/i18n-translation-management"><img src="https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/i18n-translation-management.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.01462 | $0.01462 |
| Opus 5.5 | $0.00585 | $0.00585 |
| Sonnet 5.5 | $0.00292 | $0.00292 |
| Haiku 4.5 | $0.00146 | $0.00146 |
Grade A, and why
hana-developer-cli-tool-example i18n-translation-management.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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
i18n Translation Management Guidelines
Use this guide whenever adding, updating, or removing text elements from the _i18n/ directory.
Scope and Structure
The _i18n/ folder contains properties files for multi-language support:
- Base files:
{feature}.properties(English) - Language variants:
{feature}_{code}.properties_de.properties→ German (Deutsch)_es.properties→ Spanish (Español)_fr.properties→ French (Français)_ja.properties→ Japanese (日本語)_ko.properties→ Korean (한국어)_pt.properties→ Portuguese (Português)
Example: examples.properties, examples_de.properties, examples_es.properties, examples_fr.properties, examples_ja.properties, examples_ko.properties, examples_pt.properties
Key Principle
ALL language files for a feature must contain identical keys. When adding a key to the base file, you MUST add the same key to all six language variants with appropriate translations. Never create incomplete language sets.
Adding New Text Elements
Step 1: Add to Base File
Edit the English base file (e.g., _i18n/examples.properties):
# Add your new key and English value
newKey=English text here
anotherKey=Another English string
Step 2: Add to All Language Variants
For EACH language (_de.properties, _es.properties, _fr.properties, _pt.properties):
# _i18n/examples_de.properties
newKey=Deutscher Text hier
anotherKey=Ein weiterer deutscher String
# _i18n/examples_es.properties
newKey=Texto en español aquí
anotherKey=Otra cadena en español
### Step 2: Add to All Language Variants
For EACH language (`_de.properties`, `_es.properties`, `_fr.properties`, `_ja.properties`, `_ko.properties`, `_pt.properties`):
```properties
# _i18n/examples_de.properties
newKey=Deutscher Text hier
anotherKey=Ein weiterer deutscher String
# _i18n/examples_es.properties
newKey=Texto en español aquí
anotherKey=Otra cadena en español
# _i18n/examples_fr.properties
newKey=Texte français ici
anotherKey=Une autre chaîne en français
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 · 185 lines · 1,462 tokens per session scan A dbc100d7d261
hana-developer-cli-tool-example i18n-translation-management.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,462 tokens to every session, about $0.0058 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.