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/utility-module-development.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/utility-module-development)<a href="https://agentmods.dev/instructions/sap-samples/hana-developer-cli-tool-example/utility-module-development"><img src="https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/utility-module-development/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/utility-module-development"><img src="https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/utility-module-development.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.03861 | $0.03861 |
| Opus 5.5 | $0.01544 | $0.01544 |
| Sonnet 5.5 | $0.00772 | $0.00772 |
| Haiku 4.5 | $0.00386 | $0.00386 |
Grade A, and why
hana-developer-cli-tool-example utility-module-development.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 — 624 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Utility Module Development Guidelines
Use this guide when creating or modifying JavaScript utility files in the utils/ directory (excluding utils/database/ which has separate instructions).
Scope and Purpose
This guide applies to shared utility modules in utils/ that provide common functionality across CLI commands, routes, and other components. Key modules include:
base.js/base-lite.js- Core functionality and database connectionsconnections.js- Connection parameter resolutionlocale.js- Locale detection and normalizationsqlInjection.js- SQL injection preventioncommandSuggestions.js- Command suggestion systemconfig-loader.js- Configuration file loadingmassConvert.js,massExport.js, etc. - Bulk operation utilitiesdbInspect.js- Database schema inspectiondoc-linker.js- Documentation cross-linkingversionCheck.js- Version validation
Critical Principles
- Type Safety: Use
@ts-checkand JSDoc annotations for type information - Lazy Loading: Defer expensive imports until needed to optimize startup time
- Internationalization: All user-facing strings must use
bundle.getText() - Error Handling: Provide clear, actionable error messages with context
- Debug Support: Use
base.debug()for diagnostic logging - Caching: Implement intelligent caching for expensive operations
- Pure Functions: Prefer stateless functions with predictable behavior
- Configuration: Support configuration overrides from config files
File Structure Template
/*eslint-env node, es6 */
// @ts-check
/**
* @module moduleName - Brief description of module purpose
*/
// Standard imports
import * as base from "./base.js"
import * as fs from 'fs'
import * as path from 'path'
// Module-level state (minimize)
const cache = new Map()
/**
* Main function documentation
* @param {string} param1 - Description
* @param {number} [param2] - Optional parameter
* @returns {Promise<ReturnType>} Description of return value
*/
export async function mainFunction(param1, param2) {
base.debug(base.bundle.getText("debug.call", ["mainFunction"]))
try {
// Implementation
return result
} catch (error) {
throw new Error(base.bundle.getText("error.specificError", [param1]))
}
}
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 · 624 lines · 3,861 tokens per session scan A 50927a413c9b
hana-developer-cli-tool-example utility-module-development.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,861 tokens to every session, about $0.0154 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.