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

.github/instructions/package-json-scripts.instructions.md

hana-developer-cli-tool-example package-json-scripts.instructions.md is an instructions file for GitHub Copilot from SAP-samples/hana-developer-cli-tool-example. It costs 4,985 tokens per session, scanned C, original, Apache-2.0.

A set of rules for adding or changing npm scripts, which are named commands stored in package.json for tasks such as development, testing, and building.

In plain words
What is it for?
Use it when editing package.json scripts, including scripts in workspace packages, monorepos, or continuous-integration pipelines.
Why use it?
It prevents script names, environment variables, lifecycle hooks, exit codes, and commands from becoming inconsistent across operating systems and projects.

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 "postinstall": "[ -f scripts/postinstall.js ] && node scripts/postinstall.js || echo 'No postinstall script'",.

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/package-json-scripts.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 package-json-scripts.instructions.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/sap-samples/hana-developer-cli-tool-example/package-json-scripts"><img src="https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/package-json-scripts.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 4,985 This file is loaded in full into every session.
When invoked 4,985 The same file — it is already loaded in full.
Security scan C 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.04985 $0.04985
Opus 5.5 $0.01994 $0.01994
Sonnet 5.5 $0.00997 $0.00997
Haiku 4.5 $0.00498 $0.00498

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

Security

Grade C, and why

hana-developer-cli-tool-example package-json-scripts.instructions.md scanned grade C 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

"clean": "rm -rf dist coverage", // Fails on Windows
.github/instructions/package-json-scripts.instructions.md · 703 lines

How it starts

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

Package.json Scripts Management Guidelines

Use this guide when creating or modifying npm scripts in package.json.

Scope and Purpose

This guide applies to npm script management in:

  • Root package.json - Main project scripts
  • Subproject package.json files (e.g., mcp-server/package.json)
  • Workspace package.json files in monorepos

Critical Principles

  1. Naming Convention: Use consistent, predictable script names
  2. Category Prefixes: Group related scripts with prefixes (test:*, build:*, docs:*)
  3. Cross-Platform: Write scripts that work on Windows, macOS, and Linux
  4. Composability: Build complex scripts from simpler ones
  5. Lifecycle Hooks: Use npm lifecycle scripts appropriately
  6. Environment Variables: Handle variables safely and consistently
  7. Documentation: Add comments in package.json for complex scripts
  8. Exit Codes: Respect exit codes for CI/CD integration

Script Naming Conventions

Pattern: Standard Script Names

{
  "scripts": {
    // Development
    "start": "node index.js",        // Primary entry point
    "dev": "nodemon index.js",       // Development with watch
    "serve": "node server.js",       // Start server
    
    // Building
    "build": "tsc",                  // Main build
    "build:watch": "tsc --watch",    // Watch mode
    "prebuild": "npm run clean",     // Runs before build
    "postbuild": "npm run types",    // Runs after build
    
    // Testing
    "test": "mocha",                 // Run all tests
    "test:unit": "mocha tests/unit", // Unit tests only
    "test:integration": "mocha tests/integration",
    "test:watch": "mocha --watch",   // Watch mode
    "pretest": "npm run lint",       // Runs before test
    
    // Code Quality
    "lint": "eslint .",              // Lint all files
    "lint:fix": "eslint . --fix",    // Auto-fix
    "format": "prettier --write .",  // Format code
    "format:check": "prettier --check .",
    
    // Coverage
    "coverage": "nyc npm test",      // Generate coverage
    "coverage:report": "nyc report --reporter=html",
    "coverage:check": "nyc check-coverage",
    
    // Documentation
    "docs": "npm run docs:dev",      // Alias for main docs task
    "docs:dev": "vitepress dev docs",
    "docs:build": "vitepress build docs",
    "docs:preview": "vitepress preview docs",
    
    // Cleaning
    "clean": "rimraf dist coverage .nyc_output types",
    "clean:all": "npm run clean && rimraf node_modules",
    
    // Utilities
    "validate": "npm run lint && npm run test",
    "prepare": "husky install"       // Lifecycle hook
  }
}

Read the full file on GitHub · 703 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 · 703 lines · 4,985 tokens per session scan C f122e58a21df

Subscribe to this mod's changes

hana-developer-cli-tool-example package-json-scripts.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 4,985 tokens to every session, about $0.0199 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). 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