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/testinggit clone --depth 1 https://github.com/SAP-samples/hana-developer-cli-tool-exampleWhat 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.03615 | $0.03615 |
| Opus 5 | $0.01808 | $0.01808 |
| Sonnet 5 | $0.00723 | $0.00723 |
| Haiku 4.5 | $0.00362 | $0.00362 |
Grade A, and why
hana-developer-cli-tool-example testing.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 yesterday.
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.exec('node bin/command.js --limit -5 --quiet', How it starts
The opening of the file, as written. The whole thing — 531 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Guidelines
Use this guide when creating or updating test files for this project. Tests validate CLI commands, utilities, routes, and error handling to ensure reliability and prevent regressions.
Scope and Test Types
This project contains multiple test types:
- CLI Command Tests - Validate
bin/*.jscommands via subprocess execution - Unit Tests - Test individual utility functions in isolation
- Integration Tests - Test routes and Express app functionality using
appFactory - Error Handling Tests - Validate graceful error scenarios and edge cases
- Flag Validation Tests - Verify command-line argument parsing and constraints
Test Framework and Configuration
- Test Runner: Mocha (
@latest) - Assertion Library: Node.js built-in
assertmodule - Reporting:
mochawesomefor HTML reports - Execution: Parallel (16 jobs) via
.mocharc.json - Coverage Tool:
mochawesomewith context injection - Timeout: Default 10 seconds (set per describe/it block as needed)
Configuration file: .mocharc.json
{
"timeout": "10s",
"parallel": true,
"jobs": 16,
"reporter": "spec",
"exit": true,
"require": ["./tests/helper.js"]
}
File Naming and Organization
- Naming: Use
FileName.Test.jsorfileName.test.jspattern (flexible casing +.Test.jsor.test.jssuffix) - Location: Tests live in
tests/directory, mirroring source structure - Grouping: Organize related tests in subdirectories:
tests/- CLI command teststests/utils/- Utility function teststests/routes/- Route integration tests
Examples:
- CLI command:
tests/tables.Test.js(testsbin/tables.js) - Utility test:
tests/utils/base.Test.js - Route test:
tests/routes/api.test.js - Utility helper:
tests/utils/connections.Test.js
Test Structure Template
CLI Command Tests
CLI tests execute commands via subprocess and validate output:
// @ts-check
/**
* @module commandName - Tests for bin/commandName.js
*
* Validates command-line execution, flag parsing, help output,
* and integration with the CLI framework.
*/
import * as base from './base.js'
describe('commandName', function () {
it("returns help output", function (done) {
const localTest = base.myTest.bind(this)
localTest("node bin/commandName.js --help", done)
})
it("returns normal output", function (done) {
const localTest = base.myTest.bind(this)
localTest("node bin/commandName.js --quiet", done)
})
it("accepts and uses limit flag", function (done) {
const localTest = base.myTest.bind(this)
localTest("node bin/commandName.js --limit 10 --quiet", 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.
- yesterday First seen · 531 lines · 3,615 tokens per session scan A 93b54e210123
hana-developer-cli-tool-example testing.instructions.md is an instructions file published in the GitHub repository SAP-samples/hana-developer-cli-tool-example (109 stars, last pushed 6d ago), licensed Apache-2.0. It adds 3,615 tokens to every session, about $0.0181 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/).
docs-mcp-server AGENTS.md
Instructions for arabold/docs-mcp-server, covering agent instructions for docs-mcp-server, repository context, development workflow, key commands and git workflow.