Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/sap-samples/hana-developer-cli-tool-example/test-utilities-reusegit 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/test-utilities-reuse)<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="Measured on agentmods" 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 | $0.05908 | $0.05908 |
| Opus 5 | $0.02954 | $0.02954 |
| Sonnet 5 | $0.01182 | $0.01182 |
| Haiku 4.5 | $0.00591 | $0.00591 |
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 3d 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': { 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:
-
assert- Node.js built-in assertion libraryassert.strictEqual(actual, expected) assert.deepStrictEqual(obj1, obj2) assert.ok(value) assert.throws(() => { /* code */ }, /error pattern/) -
addContext- Mochawesome context injection for HTML reportsaddContext(this, { title: 'Debug Info', value: data }) -
exec- Child process execution for subprocess testingexec('command', (error, stdout, stderr) => { /* callback */ }) -
fork- Child process fork for concurrent executionfork('script.js', args, options) -
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) })
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.
- 3d ago First seen · 918 lines · 5,908 tokens per session scan A b26779435c30
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 (109 stars, last pushed 8d ago), licensed Apache-2.0. It adds 5,908 tokens to every session, about $0.0295 per session on Opus 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.
Other instructions, from other repositories
rtk CLAUDE.md
Claude Code instructions for rtk-ai/rtk, covering claude.md, project overview, name collision warning, development commands and build & run.
rtk copilot-instructions.md
Copilot instructions for rtk-ai/rtk, covering copilot instructions for rtk, using rtk in this session, instead of: use, build, test & lint and pre-commit gate (must all pass before any pr).
awesome-vscode CLAUDE.md
Instructions for viatsko/awesome-vscode, covering claude.md, what this repo is, adding an entry, themes and linting / ci.
vscode-peacock AGENTS.md
Instructions for johnpapa/vscode-peacock, covering peacock — agent guide, project overview, repository structure, tech stack and build & run.
cs CLAUDE.md
Instructions for boyter/cs, covering claude.md, project overview, build & test commands, architecture and query pipeline (pkg/search/).
vscode-angular-snippets AGENTS.md
Instructions for johnpapa/vscode-angular-snippets, covering angular snippets for vs code — agent guide, repository structure, tech stack, build & run and test in browser (vscode.dev mode).