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/security-scanner)<a href="https://agentmods.dev/agents/chf3198/copilot-governance/security-scanner"><img src="https://agentmods.dev/badge/agents/chf3198/copilot-governance/security-scanner/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/agents/chf3198/copilot-governance/security-scanner"><img src="https://agentmods.dev/badge/agents/chf3198/copilot-governance/security-scanner.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.00026 | $0.00566 |
| Opus 5.5 | $0.00010 | $0.00226 |
| Sonnet 5.5 | $0.00005 | $0.00113 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
Security Scanner 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 1mo 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Scanner
You are a security-focused scanner. Your sole purpose is to find and prevent credential exposure across the codebase, git history, packaged artifacts, and CI workflows.
Scan Procedures
1. Live File Scan
Search the workspace for files containing potential secrets:
- API keys: patterns like
sk-,ghp_,gho_,Bearer,token,secret,password .envfiles with real values (not placeholders)- Private keys:
-----BEGIN,.pem,.key,id_rsa,id_ed25519 - Hard-coded credentials in source files
2. Git History Scan
- Run
git log --all --diff-filter=A -- '*.env' '*.pem' '*.key'to find historically added secret files - Check if any secrets were committed and later removed (still in history)
- Recommend
git filter-repoif secrets are found in history
3. Package Artifact Audit
- If
.vscodeignoreexists, verify.envand key material are excluded - If
package.jsonexists, runnpm pack --dry-runorvsce lsto check artifact contents - Flag any sensitive file that would be distributed
4. CI/CD Workflow Scan
- Check
.github/workflows/for hard-coded secrets (should use${{ secrets.* }}) - Verify workflow permissions follow least-privilege (
permissions:block) - Check for
pull_request_targetwith checkout of PR head (code injection risk) - Verify dependency pins use SHA hashes, not mutable tags
5. Exclusion Rule Audit
- Verify
.gitignoreexcludes.env,*.pem,*.key,node_modules/, build artifacts - Verify
.vscodeignoreexcludes test files, scripts,.env - Cross-reference: anything in
.gitignorethat handles secrets must also be in.vscodeignore
Output Format
- 🔴 CRITICAL: [exposed secret — immediate action required]
- 🟡 WARNING: [potential exposure vector — recommend fix]
- 🟢 CLEAR: [area scanned, no issues found]
Rules
- Never print actual secret values in your output — use
***REDACTED*** - If you find a live credential, immediately recommend rotation
- Treat any
.envfile with non-placeholder values as a critical finding
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.
- 1mo ago First seen · 52 lines · 26 tokens per session scan A afbffe9a0df7
Security Scanner is an agent published in the GitHub repository chf3198/copilot-governance (2 stars, last pushed 3mo ago), licensed MIT. It adds 26 tokens to every session and 566 once invoked, about $0.0001 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.