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/i18n-translation-managementgit 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.svg" alt="Measured on agentmods" 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 | $0.00731 | $0.00731 |
| Sonnet 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 5d 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.
- 5d 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 (109 stars, last pushed 3d ago), licensed Apache-2.0. It adds 1,462 tokens to every session, about $0.0073 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
sap-community-activity-badges flp-frontend.instructions.md
Use when working on the SAPUI5 Fiori Launchpad frontend apps (selfie, profile, tags). Covers component structure, MVC patterns, and i18n for UI5 apps.
sap-community-activity-badges i18n.instructions.md
Use when adding or modifying i18n translation strings in message bundles. Covers locale coverage, file format, and interpolation.
coder CLAUDE.md
Claude Code instructions for coder/coder, a project described as: Secure environments for developers and their agents.
Meta-Spatial-SDK-Samples AGENTS.md
AGENTS.md instructions for meta-quest/Meta-Spatial-SDK-Samples, covering meta spatial sdk — samples and docs.
vscode-gitlens CLAUDE.md
Claude Code instructions for gitkraken/vscode-gitlens, a project described as: Supercharge Git inside VS Code and unlock untapped knowledge within each repository — Visualize code authorship at a glance via Git blame annotations and CodeLens, seamlessly navigate and explore Git repositories, gain valuable insights via…
ClaudeCodeUsage AGENTS.md
Instructions for ClaudeCodeUsage/ClaudeCodeUsage, covering agents.md, product identity and scope, architecture boundaries, safety and privacy invariants and codex beta data and performance invariants.