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/ci-cd-workflows.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/ci-cd-workflows)<a href="https://agentmods.dev/instructions/sap-samples/hana-developer-cli-tool-example/ci-cd-workflows"><img src="https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/ci-cd-workflows/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/ci-cd-workflows"><img src="https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/ci-cd-workflows.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.05627 | $0.05627 |
| Opus 5.5 | $0.02251 | $0.02251 |
| Sonnet 5.5 | $0.01125 | $0.01125 |
| Haiku 4.5 | $0.00563 | $0.00563 |
Grade A, and why
hana-developer-cli-tool-example ci-cd-workflows.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 — 1,027 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD Pipeline Guidelines
Use this guide when creating, modifying, or troubleshooting GitHub Actions workflows for this project.
Scope and Purpose
This guide applies to all GitHub Actions workflow files in .github/workflows/:
- deploy-docs.yml - Documentation deployment to GitHub Pages
- cross-platform-tests.yml - Multi-OS, multi-Node.js version testing
- Future workflow files
Existing Workflows
1. Deploy Documentation (deploy-docs.yml)
Purpose: Automatically deploy VitePress documentation to GitHub Pages
Triggers:
- Push to
mainorFeb2026branches - Changes in
docs/**or workflow file - Manual trigger via
workflow_dispatch
Jobs:
- build - Build VitePress documentation
- deploy - Deploy to GitHub Pages
Key Features:
- Node.js 20 with npm caching
- Artifact upload with 1-day retention
- Permissions: read contents, write pages, id-token
Usage:
- Automatic on push to tracked branches
- Manual: Actions tab → Deploy Documentation → Run workflow
Troubleshooting Common Issues:
Issue: Build fails with "Module not found"
# Solution: Check docs/package.json dependencies
cd docs
npm ci
npm run docs:build
Issue: Deployment fails with permission error
- Check repository Settings → Pages → Source is "GitHub Actions"
- Verify workflow has
pages: writepermission
Issue: Documentation not updating
- Check artifact was uploaded successfully
- Verify deploy job ran after build job
- Clear browser cache (Ctrl+Shift+R)
2. Cross-Platform Tests (cross-platform-tests.yml)
Purpose: Test hana-cli across operating systems and Node.js versions
Triggers:
- Push to
main,master, ordevelopbranches - Pull requests to these branches
- Manual trigger via
workflow_dispatch
Matrix Strategy:
- Operating Systems: Ubuntu, Windows, macOS
- Node.js Versions: 22.x, 24.x
- Total Combinations: 6 test runs per trigger
Jobs:
1. test - Run platform-specific tests
- Install dependencies with
npm ci - Run linter (continue-on-error: true)
- Execute
npm run test:platform - Upload test results and coverage artifacts
- Upload coverage to Codecov (Ubuntu + Node 22.x only)
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 · 1,027 lines · 5,627 tokens per session scan A 587724d87cb4
hana-developer-cli-tool-example ci-cd-workflows.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,627 tokens to every session, about $0.0225 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.