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/typescript-configurationgit 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.04270 | $0.04270 |
| Opus 5 | $0.02135 | $0.02135 |
| Sonnet 5 | $0.00854 | $0.00854 |
| Haiku 4.5 | $0.00427 | $0.00427 |
Grade A, and why
hana-developer-cli-tool-example typescript-configuration.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 — 655 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript Configuration Guidelines
Use this guide when creating or modifying TypeScript configuration files (tsconfig.json) in the project.
Scope and Purpose
This guide applies to TypeScript configuration in:
- Root
tsconfig.json- Type generation from JavaScript sources mcp-server/tsconfig.json- TypeScript source compilation- Subdirectory-specific TypeScript configs
- Build-specific TypeScript configs (e.g.,
tsconfig.build.json)
Critical Principles
- Dual Config Strategy: Root config for type generation, subproject configs for compilation
- ESM Compatibility: Use Node16/NodeNext module resolution for ESM projects
- Strict Mode: Enable strict type checking for maximum safety
- Declaration Files: Generate
.d.tsfiles for external consumption - Source Maps: Enable source maps for debugging compiled code
- Incremental Builds: Use incremental compilation for faster rebuilds
- Path Mappings: Configure path aliases for clean imports
- Type-Only Imports: Use
"importsNotUsedAsValues": "error"to enforce type-only imports
Root Configuration Pattern (Type Generation from JS)
Pattern: Generate Types from JavaScript Sources
This project uses JavaScript with JSDoc comments for the main CLI. TypeScript is configured to extract type definitions:
{
"compilerOptions": {
// Enable type checking and declaration generation from JS
"allowJs": true, // Process .js files
"checkJs": true, // Type-check .js files
"declaration": true, // Generate .d.ts files
"emitDeclarationOnly": true, // ONLY generate declarations
// Module system
"module": "ESNext", // Use latest ECMAScript modules
"moduleResolution": "node", // Node.js style resolution
"target": "ES2022", // Modern JavaScript features
// Output configuration
"outDir": "./types", // Type declarations go here
"rootDir": ".", // Source root
// Type checking strictness
"strict": false, // Lenient for JS sources
"noImplicitAny": false, // Allow implicit any in JS
"strictNullChecks": false, // No null checks for JS
// Other options
"esModuleInterop": true, // CommonJS/ESM interop
"skipLibCheck": true, // Skip library type checks
"forceConsistentCasingInFileNames": true,
"resolveJsonModule": true // Import JSON files
},
"include": [
"bin/**/*.js",
"routes/**/*.js",
"utils/**/*.js",
"index.js"
],
"exclude": [
"node_modules",
"tests",
"coverage",
"types",
"**/*.test.js",
"**/*.Test.js"
]
}
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 · 655 lines · 4,270 tokens per session scan A 56cc25271371
hana-developer-cli-tool-example typescript-configuration.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 4,270 tokens to every session, about $0.0214 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.