agent-ebpf github-actions-ci.instructions.md

A guide for GitHub Actions, GitHub's system for automatically running builds and tests. It helps inspect failed workflows and reproduce their jobs locally, including with the act tool.

In plain words
What is it for?
Use it to diagnose failing workflow steps, reproduce CI jobs locally, and run checks before sending changes to GitHub.
Why use it?
It reduces guesswork when code passes on a developer's machine but fails in automated checks. Local reproduction can make the cause easier to isolate before pushing again.

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/ourobx/agent-ebpf/github-actions-ci
Clone the repo
git clone --depth 1 https://github.com/ourobx/agent-ebpf

Made for: GitHub Copilot.

Per session 752 This file is loaded in full into every session.
When invoked 752 The same file — it is already loaded in full.
Security scan D 2 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.00752 $0.00752
Opus 5 $0.00376 $0.00376
Sonnet 5 $0.00150 $0.00150
Haiku 4.5 $0.00075 $0.00075

Measured yesterday against content hash dde6c9ba9d25, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade D, and why

agent-ebpf github-actions-ci.instructions.md scanned grade D with 2 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 yesterday.

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.

Hidden instructionshighPrompt injection

Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.

<!-- Copilot Instruction Telemetry: This file was auto-generated by Claude Skills Manager -->

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

| `xvfb-run: not found` | Integration test on headless Linux | Add `sudo apt-get install -y xvfb` step |
.github/instructions/github-actions-ci.instructions.md · 80 lines

How it starts

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

github-actions-ci

GitHub Actions CI

Use when debugging GitHub Actions pipeline failures or reproducing CI stages locally before pushing.

Replaces: ci-pipeline-debug and ci-preflight (merged in v1.0.83).

Scope

  • Workflows in .github/workflows/*.yml / .github/workflows/*.yaml
  • GitHub Actions runners (ubuntu-latest, windows-latest, macos-latest)
  • actions/checkout, actions/setup-node, actions/upload-artifact and other official actions

Debug Failures

Step 1 — Read the failing step output:

gh run view <run-id> --log-failed

Or open the Actions tab → select the failed run → expand the failed step.

Step 2 — Reproduce locally (act):

act push --job <job-name> --secret-file .secrets

Step 3 — Common failure patterns:

Symptom Likely Cause Fix
npm ci fails package-lock.json out of sync npm install locally, commit lockfile
xvfb-run: not found Integration test on headless Linux Add sudo apt-get install -y xvfb step
TypeScript compile error in CI but not local Node version mismatch Align node-version across all jobs
ENOENT on artifact path if-no-files-found: error + build failed Check prior compile/package step
secret is not set PAT not added to repo secrets Settings → Secrets and variables → Actions

Pre-Flight Checklist (run before pushing)

# Compile
npm run compile

# Unit tests (matches CI unit job)
npm test

# Integration (matches CI integration job — requires xvfb on Linux/WSL)
xvfb-run -a npm run test:integration   # Linux/WSL
npm run test:integration               # Windows (no xvfb needed)

# Package (matches publish job)
npm run package
ls -la *.vsix

Node Version Consistency

Ensure all CI jobs use the same node-version. In this repo both unit and integration jobs in ci.yml must match the version in publish-extension.yml (currently Node 22). Mismatches cause silent test-passes-in-CI / prod-failures.

Read the full file on GitHub · 80 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. yesterday First seen · 80 lines · 752 tokens per session scan D dde6c9ba9d25

Subscribe to this mod's changes

agent-ebpf github-actions-ci.instructions.md is an instructions file published in the GitHub repository ourobx/agent-ebpf (1 stars, last pushed 7d ago), licensed MIT. It adds 752 tokens to every session, about $0.0038 per session on Opus 5. A static security scan graded it D with 2 findings (hidden instructions, asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.