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.
npx agentmods add skills/chf3198/copilot-governance/github-actions-security-hardeningnpx skills add chf3198/copilot-governance --skill github-actions-security-hardeninggit 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/skills/chf3198/copilot-governance/github-actions-security-hardening)<a href="https://agentmods.dev/skills/chf3198/copilot-governance/github-actions-security-hardening"><img src="https://agentmods.dev/badge/skills/chf3198/copilot-governance/github-actions-security-hardening.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.00033 | $0.00604 |
| Opus 5 | $0.00016 | $0.00302 |
| Sonnet 5 | $0.00007 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
github-actions-security-hardening 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 5d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Actions Security Hardening
Purpose
Reduce CI/CD and workflow supply-chain risk while preserving delivery velocity.
Core controls
GITHUB_TOKENleast privilege (default read, elevate per-job only when required).- Third-party actions pinned to full commit SHA where policy requires.
- Secrets hygiene (least privilege, rotation, masking, no plaintext leakage).
- OIDC preferred over long-lived cloud credentials.
- CODEOWNERS coverage for
.github/workflows/. - Dependency and vulnerability monitoring for Actions dependencies.
- Runner strategy hardening (hosted preferred for untrusted PRs; strict controls for self-hosted).
- Optional: block or limit Actions ability to create/approve PRs where policy requires.
Hard constraints
- No auto-remediation that broadens permissions.
- No direct write changes to production deployment workflows without explicit approval trail.
- If workflow trust boundaries are unclear, return
NO_CHANGE.
Output contract
ACTIONS_SECURITY_REPORT
mode: <audit|plan|remediate|verify>
scope: <repo|org>
runner: <hosted|self-hosted|mixed>
policy_profile: <strict|standard|light>
checks:
- id: A1
control: <token-permissions|pinning|oidc|...>
result: <pass|fail|partial>
evidence: <file/setting/observation>
risk: <low|medium|high>
actions:
1) priority: <P1|P2|P3>
change: <specific remediation>
verification: <objective check>
decision:
- <apply|defer|NO_CHANGE>
missing_evidence:
- <none or required artifacts>
Invocation policy
Run in pre-merge for workflow/security-sensitive changes and in periodic governance audits.
Repo workflow inventory
| Workflow | Trigger | Permissions | Status |
|---|---|---|---|
.github/workflows/lint.yml |
PR/push to main | default read | ✅ active |
.github/workflows/label-lint.yml |
issues events | issues:write, contents:read |
✅ active (ADR-010) |
label-lint.yml enforces ADR-010 rules 1–4 on every issue event. Any violation
posts an explanatory comment and fails the check. See
research/adr/010-ticket-status-role-model.md.
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.
- 5d ago First seen · 74 lines · 33 tokens per session scan A 0d2f4084fb82
github-actions-security-hardening is a skill published in the GitHub repository chf3198/copilot-governance (1 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 604 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 skills, from other repositories
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
desktop-principles
Desktop-specific UX principles - hover states, pointer precision, keyboard shortcuts, multi-window, focus management. Covers macOS, Windows, Linux, web desktop.
atmos-cache
Atmos caching: CI cache configuration and commands, GitHub Actions cache integration, Terraform registry cache mirror/list/prune/stats/trust, and cache modernization guidance.
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.