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/ci-cd-workflowsgit 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.05627 | $0.05627 |
| Opus 5 | $0.02814 | $0.02814 |
| Sonnet 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 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.
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.
- 3d 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 (109 stars, last pushed 7d ago), licensed Apache-2.0. It adds 5,627 tokens to every session, about $0.0281 per session on Opus 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
pueue AGENTS.md
Instructions for Nukesor/pueue: This project does not approve of large-scale work done by LLMs.
ClaudeCodeUsage AGENTS.md
Instructions for ClaudeCodeUsage/ClaudeCodeUsage, covering agents.md, product identity and scope, architecture boundaries, safety and privacy invariants and codex beta data and performance invariants.
vscode-gitlens CLAUDE.md
Claude Code instructions for gitkraken/vscode-gitlens, a project described as: Supercharge Git inside VS Code and unlock untapped knowledge within each repository — Visualize code authorship at a glance via Git blame annotations and CodeLens, seamlessly navigate and explore Git repositories, gain valuable insights via…
kubevirt-tekton-tasks AGENTS.md
Instructions for kubevirt/kubevirt-tekton-tasks, covering kubevirt tekton tasks - project guide, jira task management, documentation, project structure and key relationships.
docker-zoneminder CLAUDE.md
Instructions for jantman/docker-zoneminder, covering claude.md, project overview, build and test, ci/cd and architecture.
Meta-Spatial-SDK-Samples meta-quest.instructions.md
Instructions for meta-quest/Meta-Spatial-SDK-Samples: For this repository, prefer Meta Quest Agentic Tools, the Meta Horizon VS Code/Cursor extension, and the hzdb MCP server.