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/connection-pooling-timeout-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/connection-pooling-timeout-management)<a href="https://agentmods.dev/instructions/sap-samples/hana-developer-cli-tool-example/connection-pooling-timeout-management"><img src="https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/connection-pooling-timeout-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/connection-pooling-timeout-management"><img src="https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/connection-pooling-timeout-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.03452 | $0.03452 |
| Opus 5.5 | $0.01381 | $0.01381 |
| Sonnet 5.5 | $0.00690 | $0.00690 |
| Haiku 4.5 | $0.00345 | $0.00345 |
Grade A, and why
hana-developer-cli-tool-example connection-pooling-timeout-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 — 506 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Connection Pooling and Timeout Management Guidelines
Use this guide when creating or modifying code that establishes, manages, or disconnects database connections. This applies to CLI commands (bin/), API routes (routes/), and tests (tests/).
Scope and Purpose
This guide establishes standards for:
- Configurable timeout values (connection, query, operation, disconnect)
- Graceful connection lifecycle management (establishment, usage, cleanup)
- Error handling and recovery patterns
- Connection pooling best practices
- Multi-database support (HANA, PostgreSQL, SQLite)
Critical Principles
-
No Hard-Coded Timeouts: All timeout values must be configurable via environment, constructor, or options parameters. Default values are acceptable; hard-coded values are not.
-
Proper Cleanup in All Paths: Connections must be explicitly closed/disconnected in success, error, and timeout scenarios. Use try/finally blocks to guarantee cleanup.
-
Graceful Degradation on Timeout: Don't kill the entire process (
process.exit()) on operation timeouts. Instead, throw an exception that can be caught and handled appropriately by the caller or error middleware. -
Connection Establishment Timeout: Explicitly set a timeout for creating new connections to prevent indefinite hangs if the database is unreachable or unresponsive.
-
Distinct Timeout Layers: Implement timeouts at three levels:
- Connection timeout (establishing the connection)
- Query/operation timeout (executing a single query or operation)
- Overall operation timeout (entire command/route processing)
-
Retry Logic for Transient Failures: Implement exponential backoff for connection failures due to transient network issues, not permanent failures (authentication, invalid connection details).
-
Resource Cleanup on Exit: Ensure database connections are properly disconnected before CLI exit, web server shutdown, or test suite completion.
-
Connection State Transparency: Track and expose connection states (connecting, connected, executing, disconnecting) for debugging and monitoring.
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 · 506 lines · 3,452 tokens per session scan A 16c44df27433
hana-developer-cli-tool-example connection-pooling-timeout-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 3,452 tokens to every session, about $0.0138 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.