agent-ebpf deployment-practical.instructions.md

Deployment guidance focused on architecture and infrastructure that can be provisioned and run successfully on the first attempt.

In plain words
What is it for?
It helps plan or troubleshoot Azure deployments, Terraform changes, containers, CI/CD pipelines, and first-run or first-apply failures.
Why use it?
It replaces vague deployment advice with recommendations grounded in the repository's existing Terraform, Azure, CI/CD, container, and deployment files.

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

Made for: GitHub Copilot.

Per session 1,148 This file is loaded in full into every session.
When invoked 1,148 The same file — it is already loaded in full.
Security scan C 1 finding. 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.01148 $0.01148
Opus 5 $0.00574 $0.00574
Sonnet 5 $0.00230 $0.00230
Haiku 4.5 $0.00115 $0.00115

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

Security

Grade C, and why

agent-ebpf deployment-practical.instructions.md scanned grade C with 1 finding 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 -->
.github/instructions/deployment-practical.instructions.md · 100 lines

How it starts

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

deployment-practical

Deployment-practical

Shift from theoretical recommendations to provisionable architecture that survives a real first deploy.

When to use

  • User is deploying, planning infra, or fixing first-apply / first-run failures
  • Advice so far was generic and did not work on first attempt
  • Practical Focus is set to architecture-first or deploy-ready
  • Questions about Azure, Terraform, CI/CD, containers, or release pipelines in this repo

1. Read before advising

Scan the repo for existing deployment truth (do not invent a greenfield stack):

Look for Why
**/*.tf, backend.tf, modules/ Terraform patterns, state backend, naming
**/*.bicep, azure.yaml Azd/Bicep layout
.gitlab-ci.yml, .gitlab/ci/*.yml Pipeline stages, manual gates, deploy jobs
.github/workflows/* GH Actions deploy pattern
Dockerfile*, docker-compose* Container build and runtime
.azure/deployment-plan.md, infra/ Project-specific deploy plan
.claude/learning/runs.jsonl Known failures and fixes from past sessions

Pick one default approach aligned with what the repo already uses. Only propose a different stack if the user explicitly asks to change it.

2. Architecture-first output

When explaining or designing, deliver:

  1. Topology — resources, identities, networks, and data flow (names tied to this project)
  2. IaC placement — which files/modules change; no orphan snippets
  3. Pipeline fit — which CI stage runs plan vs apply vs deploy
  4. First-deploy blockers — RBAC, quotas, Key Vault access, state backend, secrets, region SKUs
  5. Single recommended path — not a menu of five options unless the user asked for comparison

Skip long theory unless it changes a concrete decision.

Read the full file on GitHub · 100 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 · 100 lines · 1,148 tokens per session scan C 1ab3be3cd52e

Subscribe to this mod's changes

agent-ebpf deployment-practical.instructions.md is an instructions file published in the GitHub repository ourobx/agent-ebpf (1 stars, last pushed 7d ago), licensed MIT. It adds 1,148 tokens to every session, about $0.0057 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.