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.
curl -O https://raw.githubusercontent.com/jonathan-vella/apex-accelerator/main/.github/instructions/governance-discovery.instructions.mdgit clone --depth 1 https://github.com/jonathan-vella/apex-acceleratorWrote 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/jonathan-vella/apex-accelerator/governance-discovery)<a href="https://agentmods.dev/instructions/jonathan-vella/apex-accelerator/governance-discovery"><img src="https://agentmods.dev/badge/instructions/jonathan-vella/apex-accelerator/governance-discovery/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/jonathan-vella/apex-accelerator/governance-discovery"><img src="https://agentmods.dev/badge/instructions/jonathan-vella/apex-accelerator/governance-discovery.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.00804 | $0.00804 |
| Opus 5.5 | $0.00322 | $0.00322 |
| Sonnet 5.5 | $0.00161 | $0.00161 |
| Haiku 4.5 | $0.00080 | $0.00080 |
Grade A, and why
apex-accelerator governance-discovery.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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Governance Discovery Instructions
CRITICAL: Governance constraints MUST come from the live Azure environment —
either directly through discover.py during the current run, or indirectly
through the approved scheduled workflow baseline generated from live Azure and
committed under .github/data/governance-policy-baseline.json.gz.
GATE: This is a mandatory gate. If Azure connectivity fails or policies
cannot be retrieved during live discovery, STOP and inform the user.
Do NOT generate governance constraints from assumptions.
Single exception: the user may explicitly choose the shipped alz-corp-default baseline as assumed
governance (see baseline-check.md). It must be labelled assumed and not tenant-verified in every artifact,
and the Step 3.5 review stays mandatory.
Do NOT accept arbitrary static files as governance input — only the approved
workflow output file (.github/data/governance-policy-baseline.json.gz) is valid
for cached baseline mode.
Why This Matters
Assumed governance constraints cause deployment failures. Example:
- Assumed: 4 tags required (Environment, ManagedBy, Project, Owner)
- Actual: 9 tags required via Azure Policy
- Result: Deployment denied by Azure Policy
Management group-inherited policies are invisible to basic queries.
Use REST API (not az policy assignment list) to capture all inherited policies.
Discovery Runs Through discover.py
04g-Governance runs the deterministic
discover.py (live) or
render_cached_governance.py (approved baseline). The script verifies ARM
connectivity, queries all effective assignments via REST (including
MG-inherited), drills into Deny/DeployIfNotExists definitions, classifies
effects and writes 04-governance-constraints.json. Do not re-create or
hand-populate that file.
The authoritative output contract is
tools/schemas/governance-constraints.schema.json
and the skill's field reference.
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.
- 6d ago Changed · +5 lines · +95 tokens per session ec654ca91447
- 1mo ago Changed · -4 lines · -4 tokens per session aa22a806140a
- 1mo ago First seen · 77 lines · 713 tokens per session scan A af371ef67e53
apex-accelerator governance-discovery.instructions.md is an instructions file published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed yesterday), licensed MIT. It adds 804 tokens to every session, about $0.0032 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.