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/drvoss/everything-copilot-cli/github-actions-efficiencynpx skills add drvoss/everything-copilot-cli --skill github-actions-efficiencygit clone --depth 1 https://github.com/drvoss/everything-copilot-cliWrote 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/drvoss/everything-copilot-cli/github-actions-efficiency)<a href="https://agentmods.dev/skills/drvoss/everything-copilot-cli/github-actions-efficiency"><img src="https://agentmods.dev/badge/skills/drvoss/everything-copilot-cli/github-actions-efficiency.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 | $0.00032 | $0.01174 |
| Opus 5 | $0.00016 | $0.00587 |
| Sonnet 5 | $0.00006 | $0.00235 |
| Haiku 4.5 | $0.00003 | $0.00117 |
Grade A, and why
github-actions-efficiency 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 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.
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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Actions Efficiency
Audit GitHub Actions workflow efficiency without weakening required validation. Focus on runner time, wasted runs, broad triggers, and the fastest fixes that actually hold up under review.
When to Use
- CI minutes are growing faster than the repository's actual change volume
- Workflows run too often for docs-only, workflow-only, or narrow-scope changes
- You need to optimize caches, concurrency, trigger scope, or matrix breadth
- A repository is onboarding GitHub Actions and needs a lean baseline first
- A team wants a before/after efficiency report grounded in real workflow evidence
When NOT to Use
| Instead of github-actions-efficiency | Use |
|---|---|
| Debugging one failed workflow run | actions-debugging |
| Reviewing Actions security risks | gha-security-review |
| Auditing model or token spend across AI workflows | cost-audit |
Prerequisites
- Access to
.github/workflows/ ghCLI access if you want live run data- Understanding of which checks are mandatory for release, shared libraries, or migrations
Load Only What You Need
../../../references/github-actions-efficiency/actions.md- audit order, trigger scoping, matrix reduction, and live validation guidance../../../references/github-actions-efficiency/reporting.md- before/after reporting and follow-up review passes../../../references/github-actions-efficiency/patterns.md- concrete YAML examples when inline guidance is not enough../../../references/github-actions-efficiency/review-rubric.md- review rubric for completed efficiency changes
If no workflows exist yet, start with actions.md and define a minimal baseline before trying
to optimize.
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.
- yesterday First seen · 123 lines · 32 tokens per session scan A 354574de5cec
github-actions-efficiency is a skill published in the GitHub repository drvoss/everything-copilot-cli (45 stars, last pushed 8d ago), licensed MIT. It adds 32 tokens to every session and 1,174 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-09-03.
Other skills, from other repositories
omc-ado-triage
Azure DevOps work item triage — surfaces untriaged items, active work, open PRs, pipeline failures, and security alerts. WHEN: User wants to check ADO board status, triage work items, see pipeline health, review open PRs, or get a project health overview. DO NOT USE FOR: Sprint planning (use omc-ado-sprint), PR code…
configuring-codemagic
Configures Codemagic CI/CD pipelines for Flutter using codemagic.yaml. Use when setting up automated Flutter builds on Codemagic, configuring iOS code signing without Fastlane Match, deploying to App Store Connect or Google Play from Codemagic, caching pub dependencies in Codemagic, setting up encrypted environment…
configuring-github-actions
Configures GitHub Actions CI/CD workflows for Flutter projects. Use when creating or editing .github/workflows/ YAML files for Flutter, integrating subosito/flutter-action, automating flutter test, flutter analyze, or dart format on push or pullrequest events, running buildrunner in CI, building Android AAB or iOS IPA…
ci-security-scanning-with-strix
Add security scanning to CI/CD with Strix — GitHub Actions, GitLab CI, or any pipeline — so every pull request gets a diff-scoped AI pentest that blocks vulnerable code before it merges, with results as PR comments and SARIF uploaded to code scanning. Covers both the self-hosted open-source CLI (runs in your runner)…
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…
chinese-git-workflow
国内 Git 平台配置参考——Gitee、Coding.net、极狐 GitLab、CNB 的 SSH/HTTPS/凭据/CI 接入差异与镜像同步配置。仅在用户显式 /chinese-git-workflow 时调用，不要根据上下文自动触发。.