apex-accelerator: Instructions file for GitHub Copilot

.github/instructions/github-actions.instructions.md

apex-accelerator github-actions.instructions.md is an instructions file for GitHub Copilot from jonathan-vella/apex-accelerator. It costs 922 tokens per session, scanned A, original, MIT.

Project-specific rules for GitHub Actions, the service that runs automated jobs when code changes or scheduled events occur. They cover runners, Node.js, permissions, triggers, dependencies, and action versions.

In plain words
What is it for?
Use them when creating or changing CI/CD workflows for testing, validation, scheduled checks, and other automated repository jobs.
Why use it?
They keep automation workflows consistent and reduce failures caused by outdated runtimes, excessive permissions, or unsuitable triggers.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is jonathan-vella/apex-accelerator's own configuration. It tells GitHub Copilot how to work on apex-accelerator itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything apex-accelerator configures →

Reuse

Borrowing it

Nothing to install: this file belongs to jonathan-vella/apex-accelerator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/jonathan-vella/apex-accelerator/main/.github/instructions/github-actions.instructions.md
Clone the repo
git clone --depth 1 https://github.com/jonathan-vella/apex-accelerator

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for apex-accelerator github-actions.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/jonathan-vella/apex-accelerator/github-actions/github.svg)](https://agentmods.dev/instructions/jonathan-vella/apex-accelerator/github-actions)
Your own site
<a href="https://agentmods.dev/instructions/jonathan-vella/apex-accelerator/github-actions"><img src="https://agentmods.dev/badge/instructions/jonathan-vella/apex-accelerator/github-actions/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.

agentmods 80×15 button for apex-accelerator github-actions.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/jonathan-vella/apex-accelerator/github-actions"><img src="https://agentmods.dev/badge/instructions/jonathan-vella/apex-accelerator/github-actions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 922 This file is loaded in full into every session.
When invoked 922 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00922 $0.00922
Opus 5.5 $0.00369 $0.00369
Sonnet 5.5 $0.00184 $0.00184
Haiku 4.5 $0.00092 $0.00092

Measured 6d ago against content hash b5f52c86593a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

apex-accelerator github-actions.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 6d 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-actions.instructions.md · 83 lines

How it starts

The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GitHub Actions Workflow Standards

Standards for creating and maintaining CI/CD workflows in this repository. For general GitHub Actions best practices, rely on GitHub Actions documentation.

Project Conventions

Runner and Node.js

  • Runner: ubuntu-latest for all jobs
  • Node.js: Version 24 with npm caching — never use 20 or older (Node.js 20 reached EOL April 2026)
  • Dependencies: npm ci (not npm install); reuse the composite ./.github/actions/setup-node-repo action instead of repeating setup steps

Permissions and Triggers

  • Set permissions at workflow level (least privilege); default contents: read
  • Scope triggers with paths: and include workflow_dispatch for on-demand runs
  • Add concurrency (${{ github.workflow }}-${{ github.ref }}, cancel-in-progress: true)

Action Versions

  • Pin to major version tags (e.g., @v7), never @main or @latest
  • Current versions:
Action Version
actions/checkout @v7
actions/setup-node @v7
actions/setup-python @v7
actions/upload-artifact @v7
actions/download-artifact @v8
actions/cache @v4
actions/github-script @v8
actions/dependency-review-action @v5
peter-evans/create-pull-request @v8

Existing Workflows

Workflow Purpose Trigger
ci.yml Independent repository, external-tool and secret-scan jobs PR + push to main/feature + manual
branch-enforcement.yml Contributor branch naming and change-scope checks PR to main
validate-devcontainer-base.yml Validate the devcontainer base and compare verdicts Relevant same-repository PR changes + manual
consumer-template-checks.yml Validate inactive consumer workflows Template changes + manual
upstream-skill-drift.yml Keep one issue with upstream azure-skills drift Weekly schedule + manual
dependency-security.yml Dependency review and npm/pip audit gates Dependency or workflow changes + weekly + manual

Read the full file on GitHub · 83 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. 6d ago Changed · +7 lines · +114 tokens per session b5f52c86593a
  2. 18d ago Changed · +2 lines · +47 tokens per session 0e94153f4aed
  3. 1mo ago Changed · -37 lines · -333 tokens per session 5ad7efe2b1d7
  4. 1mo ago Changed · +2 lines · +40 tokens per session 6baaab060127
  5. 1mo ago Changed · +2 lines · -20 tokens per session 4ed8714bdd77
  6. 1mo ago First seen · 107 lines · 1,074 tokens per session scan A acdfee5bc1ae

Subscribe to this mod's changes

apex-accelerator github-actions.instructions.md is an instructions file published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed yesterday), licensed MIT. It adds 922 tokens to every session, about $0.0037 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.

Related

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,786 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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).

microsoft/vscode · 2,731 tokens

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.

denoland/deno · 3,077 tokens