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

.github/instructions/test-utilities-reuse.instructions.md

hana-developer-cli-tool-example test-utilities-reuse.instructions.md is an instructions file for GitHub Copilot from SAP-samples/hana-developer-cli-tool-example. It costs 5,908 tokens per session, scanned A, original, Apache-2.0.

Guidance for writing tests that reuse the project's existing helpers, mocks, assertions, command runners, and database-testing patterns.

In plain words
What is it for?
Use it when creating or updating tests that need shared utilities for command execution, file systems, modules, databases, or external tools.
Why use it?
It avoids duplicated test code and keeps new tests consistent with the project's established testing setup.

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 →

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /home/user/.config.

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/test-utilities-reuse.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 test-utilities-reuse.instructions.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/sap-samples/hana-developer-cli-tool-example/test-utilities-reuse"><img src="https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/test-utilities-reuse.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 5,908 This file is loaded in full into every session.
When invoked 5,908 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.05908 $0.05908
Opus 5.5 $0.02363 $0.02363
Sonnet 5.5 $0.01182 $0.01182
Haiku 4.5 $0.00591 $0.00591

Measured 1mo ago against content hash b26779435c30, 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 test-utilities-reuse.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.

'child_process': {
.github/instructions/test-utilities-reuse.instructions.md · 918 lines

How it starts

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

Test Utilities Discovery and Reuse Guidelines

Use this guide when creating or updating test files to leverage the established testing infrastructure. This project has comprehensive test utilities in tests/utils/ and tests/base.js that should be discovered and reused rather than recoded.

Critical Principle: Reuse Before Recode

Always check tests/utils/ and tests/base.js for existing functionality before implementing new test helpers.

The project has:

  • Comprehensive mocking patterns for ESM modules
  • Shared assertion and reporting utilities
  • CLI command execution helpers
  • Database client testing patterns
  • File system mocking conventions
  • External CLI integration patterns (BTP, CF)

Core Test Infrastructure

Central Base Utilities (tests/base.js)

The tests/base.js file provides foundational test utilities used across all test files:

import { assert, addContext, exec, fork, myTest } from '../base.js'

Available exports:

  1. assert - Node.js built-in assertion library

    assert.strictEqual(actual, expected)
    assert.deepStrictEqual(obj1, obj2)
    assert.ok(value)
    assert.throws(() => { /* code */ }, /error pattern/)
    
  2. addContext - Mochawesome context injection for HTML reports

    addContext(this, { title: 'Debug Info', value: data })
    
  3. exec - Child process execution for subprocess testing

    exec('command', (error, stdout, stderr) => { /* callback */ })
    
  4. fork - Child process fork for concurrent execution

    fork('script.js', args, options)
    
  5. myTest(command, done) - Specialized CLI command test helper

    • Executes CLI commands via subprocess
    • Automatically filters debug output from stderr
    • Injects stdout into Mochawesome context
    • Throws on unexpected stderr content

    Usage pattern:

    it("returns help output", function (done) {
        const localTest = base.myTest.bind(this)
        localTest("node bin/commandName.js --help", done)
    })
    

Read the full file on GitHub · 918 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 · 918 lines · 5,908 tokens per session scan A b26779435c30

Subscribe to this mod's changes

hana-developer-cli-tool-example test-utilities-reuse.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,908 tokens to every session, about $0.0236 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