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.
curl -O https://raw.githubusercontent.com/SAP-samples/hana-developer-cli-tool-example/main/.github/instructions/automation-script-development.instructions.mdgit 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/automation-script-development)<a href="https://agentmods.dev/instructions/sap-samples/hana-developer-cli-tool-example/automation-script-development"><img src="https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/automation-script-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.
<a href="https://agentmods.dev/instructions/sap-samples/hana-developer-cli-tool-example/automation-script-development"><img src="https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/automation-script-development.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.04780 | $0.04780 |
| Opus 5.5 | $0.01912 | $0.01912 |
| Sonnet 5.5 | $0.00956 | $0.00956 |
| Haiku 4.5 | $0.00478 | $0.00478 |
Grade A, and why
hana-developer-cli-tool-example automation-script-development.instructions.md scanned grade A with 0 findings 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 780 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automation Script Development Guidelines
Use this guide when creating or modifying automation scripts in the scripts/ folder.
Scope and Purpose
This guide applies to automation and code generation scripts in the scripts/ folder:
Script Categories:
scripts/generate-*.js- Generate new files (docs, config, examples)scripts/enhance-*.js- Enhance existing files with extracted metadatascripts/update-*.js- Update existing files with new contentscripts/populate-*.js- Populate templates with datascripts/CHANGELOG.js- Generate changelog from JSON
Common Scripts:
scripts/generate-command-docs.js- Generate command documentationscripts/generate-sidebar-config.js- Generate VitePress sidebar configscripts/generate-examples.js- Generate example filesscripts/enhance-command-docs.js- Enhance docs with metadata from sourcescripts/update-epilogues.js- Update command epiloguesscripts/populate-command-docs.js- Populate doc templatesscripts/CHANGELOG.js- Convert CHANGELOG.json to markdown
Critical Principles
- Shebang: Start with
#!/usr/bin/env nodefor direct execution - ESM Modules: Use ES module syntax (
import/export) - Type Safety: Add
@ts-checkfor basic type checking - Safe File I/O: Check existence before reading, backup before overwriting
- Clear Logging: Provide progress updates and success/failure messages
- Exit Codes: Use proper exit codes (0=success, 1=failure)
- Idempotency: Scripts should be safe to run multiple times
- Documentation: Include JSDoc header explaining purpose
File Structure Template
#!/usr/bin/env node
/**
* Brief description of what this script does
*
* Usage: node script-name.js [options]
*
* Examples:
* node script-name.js
* node script-name.js --force
*/
import fs from 'fs'
import path from 'path'
// Node 20.11+: import.meta.dirname / import.meta.filename
const __dirname = import.meta.dirname
// Constants
const SOURCE_DIR = path.join(__dirname, 'source')
const OUTPUT_DIR = path.join(__dirname, 'output')
/**
* Main execution function
*/
async function main() {
try {
console.log('Starting script...')
// Script logic here
console.log('✅ Script completed successfully')
process.exit(0)
} catch (error) {
console.error('❌ Script failed:', error.message)
console.error(error.stack)
process.exit(1)
}
}
main()
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.
- 1mo ago First seen · 780 lines · 4,780 tokens per session scan A 03a92b3164a1
hana-developer-cli-tool-example automation-script-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 4,780 tokens to every session, about $0.0191 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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).
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.
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).
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.
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).
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.