hana-developer-cli-tool-example: Instructions file for GitHub Copilot

.github/instructions/scripts-directory-development.instructions.md

hana-developer-cli-tool-example scripts-directory-development.instructions.md is an instructions file for GitHub Copilot from SAP-samples/hana-developer-cli-tool-example. It costs 5,632 tokens per session, scanned A, original, Apache-2.0.

Instructions for creating or updating maintenance scripts in a project’s scripts/ directory. They cover command-line behavior, validation, build and test utilities, exit codes, CI use, and user messages.

In plain words
What is it for?
Use them when writing post-install, validation, build, or test scripts that need argument parsing, CI support, aggregated errors, and consistent exit codes.
Why use it?
They help scripts behave predictably in local development and automated builds, including clear failures and repeatable runs.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is SAP-samples/hana-developer-cli-tool-example's own configuration. It tells GitHub Copilot how to work on hana-developer-cli-tool-example itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything hana-developer-cli-tool-example configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is * Usage: node scripts/script-name.js [--flag] [--option value].

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/SAP-samples/hana-developer-cli-tool-example/main/.github/instructions/scripts-directory-development.instructions.md
Clone the repo
git clone --depth 1 https://github.com/SAP-samples/hana-developer-cli-tool-example

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for hana-developer-cli-tool-example scripts-directory-development.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/scripts-directory-development/github.svg)](https://agentmods.dev/instructions/sap-samples/hana-developer-cli-tool-example/scripts-directory-development)
Your own site
<a href="https://agentmods.dev/instructions/sap-samples/hana-developer-cli-tool-example/scripts-directory-development"><img src="https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/scripts-directory-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.

agentmods 80×15 button for hana-developer-cli-tool-example scripts-directory-development.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/sap-samples/hana-developer-cli-tool-example/scripts-directory-development"><img src="https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/scripts-directory-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 5,632 This file is loaded in full into every session.
When invoked 5,632 The same file — it is already loaded in full.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.05632 $0.05632
Opus 5.5 $0.02253 $0.02253
Sonnet 5.5 $0.01126 $0.01126
Haiku 4.5 $0.00563 $0.00563

Measured 1mo ago against content hash 13ac87a405e5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

hana-developer-cli-tool-example scripts-directory-development.instructions.md scanned grade A with 1 finding 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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

import { exec } from 'node:child_process'
.github/instructions/scripts-directory-development.instructions.md · 917 lines

How it starts

The opening of the file, as written. The whole thing — 917 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Scripts Directory Development Guidelines

Use this guide when creating or modifying scripts in the scripts/ directory.

Scope and Purpose

This guide applies to maintenance and utility scripts in the scripts/ directory that support development, testing, and build processes:

Script Types:

  • Postinstall scripts: Run after npm install (postinstall.js)
  • Validation scripts: Check project integrity (validate-i18n.js)
  • Build utilities: Generate documentation indices (build-docs-index.js)
  • Test utilities: Process test output (run-test-output.js)

Critical Principles

  1. Shebang: Start with #!/usr/bin/env node for npm script execution
  2. Exit Codes: Use 0 (success), 1 (validation failure), 2 (error)
  3. CI-Friendly: Detect and adapt to CI/CD environments
  4. Quiet Mode: Support --quiet flag for minimal output
  5. Internationalization: Use text bundles for user messages
  6. Error Aggregation: Collect all errors before failing
  7. Idempotent: Safe to run multiple times
  8. Self-Contained: Don't require external setup

File Structure Template

#!/usr/bin/env node

/**
 * Script purpose and description
 * 
 * This script [what it does].
 * 
 * Usage: node scripts/script-name.js [--flag] [--option value]
 * 
 * Exit codes:
 *   0 = Success
 *   1 = Validation failures or warnings
 *   2 = Fatal error (file system, parsing, etc.)
 */

import fs from 'fs'
import path from 'path'

// ESM __dirname equivalent (Node 20.11+: import.meta.dirname / import.meta.filename)
const __dirname = import.meta.dirname

// Configuration
const CONFIG = {
    rootDir: path.join(__dirname, '..'),
    targetDir: path.join(__dirname, '..', 'target'),
    // ... other config
}

// Parse arguments
const args = process.argv.slice(2)
const options = {
    quiet: args.includes('--quiet'),
    fix: args.includes('--fix'),
    help: args.includes('--help') || args.includes('-h')
}

// State tracking
let errorCount = 0
let warningCount = 0
const errors = []
const warnings = []

/**
 * Log error and track it
 * @param {string} message - Error message
 */
function logError(message) {
    errorCount++
    errors.push(message)
    if (!options.quiet) console.error(`❌ ERROR: ${message}`)
}

/**
 * Log warning and track it
 * @param {string} message - Warning message
 */
function logWarning(message) {
    warningCount++
    warnings.push(message)
    if (!options.quiet) console.warn(`⚠️  WARNING: ${message}`)
}

/**
 * Log info message
 * @param {string} message - Info message
 */
function logInfo(message) {
    if (!options.quiet) console.log(`ℹ️  ${message}`)
}

/**
 * Main execution function
 */
async function main() {
    try {
        if (options.help) {
            printHelp()
            process.exit(0)
        }

        logInfo('Starting script...')
        
        // Script logic here
        
        // Report results
        if (errorCount > 0 || warningCount > 0) {
            console.log(`\n📊 Summary: ${errorCount} errors, ${warningCount} warnings`)
            process.exit(errorCount > 0 ? 1 : 0)
        }
        
        if (!options.quiet) console.log('✅ All checks passed')
        process.exit(0)
        
    } catch (error) {
        console.error('❌ Fatal error:', error.message)
        console.error(error.stack)
        process.exit(2)
    }
}

/**
 * Print help message
 */
function printHelp() {
    console.log(`
Usage: node scripts/script-name.js [options]

Options:
  --quiet     Minimal output, only errors
  --fix       Automatically fix issues if possible
  --help, -h  Show this help message

Exit Codes:
  0 = Success
  1 = Validation failures found
  2 = Fatal error occurred
    `)
}

main()

Read the full file on GitHub · 917 lines

Changes

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.

  1. 1mo ago First seen · 917 lines · 5,632 tokens per session scan A 13ac87a405e5

Subscribe to this mod's changes

hana-developer-cli-tool-example scripts-directory-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 5,632 tokens to every session, about $0.0225 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

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).

microsoft/vscode · 9,649 tokens

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.

vercel/next.js · 7,549 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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).

microsoft/vscode · 2,731 tokens

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.

denoland/deno · 3,077 tokens