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/config-files-managementgit 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.04409 | $0.04409 |
| Opus 5 | $0.02204 | $0.02204 |
| Sonnet 5 | $0.00882 | $0.00882 |
| Haiku 4.5 | $0.00441 | $0.00441 |
Grade A, and why
hana-developer-cli-tool-example config-files-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 3d 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 — 772 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configuration Files Management Guidelines
Use this guide when creating or modifying configuration files for development tools.
Scope and Purpose
This guide applies to configuration files for:
- ESLint (
eslint.config.jsflat config) - Prettier (
.prettierrc.json,.prettierrc.js) - NYC/Istanbul coverage (
.nycrc,.nycrc.json) - Mocha testing (
.mocharc.json,.mocharc.js) - Markdown linting (
.markdownlintrc.json) - EditorConfig (
.editorconfig) - Git ignore patterns (
.gitignore,.npmignore)
Critical Principles
- Shared Configs: Extend from shared configurations when available
- Consistency: Align configs across similar projects
- Override Hierarchy: Understand config precedence and overrides
- Ignore Patterns: Maintain comprehensive ignore lists
- JSON vs JS: Choose appropriate format (JSON for simple, JS for complex)
- Comments: Use JS format when extensive comments needed
- Integration: Ensure tools work together harmoniously
- CI/CD Alignment: Config should work in both local and CI environments
ESLint Configuration
Pattern: ESLint for JavaScript with CDS Plugin
{
"env": {
"es2022": true,
"node": true,
"mocha": true
},
"extends": [
"eslint:recommended"
],
"plugins": [
"@sap/cds"
],
"parserOptions": {
"ecmaVersion": 2022,
"sourceType": "module"
},
"rules": {
// Possible Errors
"no-console": "off", // Allow console in Node.js
"no-unused-vars": [
"error",
{
"argsIgnorePattern": "^_", // Allow _unused variables
"varsIgnorePattern": "^_"
}
],
// Best Practices
"eqeqeq": ["error", "always"], // Require === and !==
"no-eval": "error", // No eval()
"no-implied-eval": "error", // No setTimeout("string")
"no-return-await": "error", // No unnecessary await
// Code Style
"indent": ["error", 4], // 4-space indentation
"quotes": ["error", "single"], // Single quotes
"semi": ["error", "always"], // Always semicolons
"comma-dangle": ["error", "never"], // No trailing commas
// CDS-specific rules
"@sap/cds/no-dollar-prefixed-names": "off"
},
"overrides": [
{
// Relaxed rules for test files
"files": ["**/*.test.js", "**/*.Test.js"],
"rules": {
"no-unused-expressions": "off" // For should/expect
}
}
],
"ignorePatterns": [
"node_modules/",
"dist/",
"coverage/",
"*.min.js",
"mochawesome-report/"
]
}
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.
- 3d ago First seen · 772 lines · 4,409 tokens per session scan A e66e25ec42dc
hana-developer-cli-tool-example config-files-management.instructions.md is an instructions file published in the GitHub repository SAP-samples/hana-developer-cli-tool-example (109 stars, last pushed 8d ago), licensed Apache-2.0. It adds 4,409 tokens to every session, about $0.0220 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
kilocode AGENTS.md
AGENTS.md instructions for Kilo-Org/kilocode, covering agents.md, build and dev, quality checks, products and package instructions.
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/).
language-tools AGENTS.md
Instructions for prisma/language-tools, covering agent guide for prisma language tools, project overview, packages, documentation and quick start.
getspecstory copilot-instructions.md
Instructions for specstoryai/getspecstory: Examine the file changes for the pull request.
vscode-gitlens AGENTS.md
AGENTS.md instructions for gitkraken/vscode-gitlens, covering gitlens development guide, working style expectations, development environment, development commands and git & repository guidelines.