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/github-workflow-maintenance.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/github-workflow-maintenance)<a href="https://agentmods.dev/instructions/sap-samples/hana-developer-cli-tool-example/github-workflow-maintenance"><img src="https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/github-workflow-maintenance/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/github-workflow-maintenance"><img src="https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/github-workflow-maintenance.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.04513 | $0.04513 |
| Opus 5.5 | $0.01805 | $0.01805 |
| Sonnet 5.5 | $0.00903 | $0.00903 |
| Haiku 4.5 | $0.00451 | $0.00451 |
Grade A, and why
hana-developer-cli-tool-example github-workflow-maintenance.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 — 802 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Workflow Maintenance Guidelines
Use this guide when creating or modifying GitHub Actions workflow files in .github/workflows/.
Scope and Purpose
This guide applies to GitHub Actions workflow configuration:
- CI/CD pipelines for testing and building
- Documentation deployment workflows
- Release automation
- Scheduled maintenance tasks
- Pull request checks
- Package publishing workflows
Critical Principles
- Matrix Testing: Use matrix strategy for testing across multiple environments
- Dependency Caching: Cache npm dependencies to speed up builds
- Artifact Management: Properly upload and download build artifacts
- Secret Security: Never expose secrets in logs or outputs
- Job Dependencies: Clearly specify job dependencies with
needs - Fail Fast: Use
fail-fast: falsefor comprehensive testing - Descriptive Names: Use clear, descriptive names for workflows and jobs
- Idempotency: Jobs should be repeatable and produce consistent results
Workflow Structure Template
name: Descriptive Workflow Name
# Trigger configuration
on:
push:
branches: [main, develop]
paths:
- 'src/**'
- 'package.json'
pull_request:
branches: [main]
workflow_dispatch: # Manual trigger
schedule:
- cron: '0 0 * * 0' # Weekly on Sunday
# Environment variables
env:
NODE_VERSION: '20'
NPM_CONFIG_LOGLEVEL: 'error'
# Workflow permissions
permissions:
contents: read
packages: write
jobs:
# Job definitions
test:
name: Test on Node ${{ matrix.node-version }}
runs-on: ${{ matrix.os }}
strategy:
fail-fast: false
matrix:
os: [ubuntu-latest, windows-latest, macos-latest]
node-version: [18, 20]
steps:
# Step definitions
- uses: actions/checkout@v4
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: ${{ matrix.node-version }}
cache: 'npm'
- name: Install dependencies
run: npm ci
- name: Run tests
run: npm test
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 · 802 lines · 4,513 tokens per session scan A 254e40aa9a39
hana-developer-cli-tool-example github-workflow-maintenance.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,513 tokens to every session, about $0.0181 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.