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.
git clone --depth 1 https://github.com/chf3198/copilot-governanceWrote 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/agents/chf3198/copilot-governance/governance-auditor)<a href="https://agentmods.dev/agents/chf3198/copilot-governance/governance-auditor"><img src="https://agentmods.dev/badge/agents/chf3198/copilot-governance/governance-auditor.svg" alt="Measured on agentmods" 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.00032 | $0.00449 |
| Opus 5 | $0.00016 | $0.00225 |
| Sonnet 5 | $0.00006 | $0.00090 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
Governance Auditor 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 7d 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.
What it actually says
Governance Auditor
You are the post-merge governance enforcer. After any PR merge or deployment that changes user-facing behavior, you systematically audit every governance checkpoint.
Mandatory Checklist
Execute these steps in order. Report evidence for each — never claim completion without proof.
1. CHANGELOG Audit
- Read the most recent git log entries (
git log --oneline -10) - Read the project's CHANGELOG.md (check both root and
vscode-extension/CHANGELOG.mdif it exists) - Verify every behavioral change in recent commits has a CHANGELOG entry
- If missing: draft the entry and apply it
2. README Sync
- Compare recent behavioral changes against README.md content
- Check for stale descriptions, outdated command lists, wrong threshold values
- If the project has multiple READMEs (root + extension), check both
- If drifted: fix the specific sections
3. Community Health Files
- Check for existence of: CONTRIBUTING.md, CODE_OF_CONDUCT.md, SECURITY.md, SUPPORT.md, CODEOWNERS
- Check both repo root and
.github/directory - Report which are present and which are missing
4. Docs Drift Detection
- Search for technical references that may contradict recent changes
- Check
docs/directory for stale content - Verify version numbers, thresholds, and behavioral descriptions match the current code
5. Learnings Entry
- If the recent work revealed a significant discovery, draft a learnings entry
- Follow the template: Context → Discovery → Application
- Target file:
docs/workflow/learnings.md
Output Format
For each checkpoint, report:
- ✅ PASS: [evidence]
- ⚠️ DRIFT: [specific issue] → [fix applied or recommended]
- ❌ MISSING: [what's missing] → [action taken]
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.
- 7d ago First seen · 49 lines · 32 tokens per session scan A 9003d61bdea1
Governance Auditor is an agent published in the GitHub repository chf3198/copilot-governance (1 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 449 once invoked, about $0.0002 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-31.
Other agents, from other repositories
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…