hana-developer-cli-tool-example github-workflow-maintenance.instructions.md

Guidance for GitHub Actions workflows, which are automated jobs that test, build, publish, deploy, or maintain a repository.

In plain words
What is it for?
Use it when creating or changing files in .github/workflows for pull requests, releases, scheduled tasks, documentation, packages, or deployments.
Why use it?
It helps workflows run consistently across environments while protecting secrets, managing job dependencies, and preserving build artifacts.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/sap-samples/hana-developer-cli-tool-example/github-workflow-maintenance
Clone the repo
git clone --depth 1 https://github.com/SAP-samples/hana-developer-cli-tool-example

Made for: GitHub Copilot.

Per session 4,513 This file is loaded in full into every session.
When invoked 4,513 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.04513 $0.04513
Opus 5 $0.02256 $0.02256
Sonnet 5 $0.00903 $0.00903
Haiku 4.5 $0.00451 $0.00451

Measured 2d ago against content hash 254e40aa9a39, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

.github/instructions/github-workflow-maintenance.instructions.md · 802 lines

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

  1. Matrix Testing: Use matrix strategy for testing across multiple environments
  2. Dependency Caching: Cache npm dependencies to speed up builds
  3. Artifact Management: Properly upload and download build artifacts
  4. Secret Security: Never expose secrets in logs or outputs
  5. Job Dependencies: Clearly specify job dependencies with needs
  6. Fail Fast: Use fail-fast: false for comprehensive testing
  7. Descriptive Names: Use clear, descriptive names for workflows and jobs
  8. 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

Read the full file on GitHub · 802 lines

Changes

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.

  1. 2d ago First seen · 802 lines · 4,513 tokens per session scan A 254e40aa9a39

Subscribe to this mod's changes

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 (109 stars, last pushed 6d ago), licensed Apache-2.0. It adds 4,513 tokens to every session, about $0.0226 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.