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 skills add jnPiyush/AgentX --skill github-actions-workflowsgit clone --depth 1 https://github.com/jnPiyush/AgentXWrote 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/jnpiyush/agentx/github-actions-workflows)<a href="https://agentmods.dev/skills/jnpiyush/agentx/github-actions-workflows"><img src="https://agentmods.dev/badge/skills/jnpiyush/agentx/github-actions-workflows/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/skills/jnpiyush/agentx/github-actions-workflows"><img src="https://agentmods.dev/badge/skills/jnpiyush/agentx/github-actions-workflows.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00052 | $0.03602 |
| Opus 5.5 | $0.00021 | $0.01441 |
| Sonnet 5.5 | $0.00010 | $0.00720 |
| Haiku 4.5 | $0.00005 | $0.00360 |
Grade A, and why
github-actions-workflows 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 — 381 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Actions & Workflows
Purpose: Concise guide for building, testing, and deploying with GitHub Actions. Detailed YAML examples live in
references/- this file covers decisions, patterns, and guardrails.
When to Use This Skill
- Creating GitHub Actions CI/CD workflows
- Building reusable workflow templates
- Configuring matrix builds and parallel jobs
- Implementing security best practices for GitHub Actions
- Troubleshooting failed workflow runs
Prerequisites
- GitHub repository with admin access
- YAML syntax knowledge
Decision Tree
What GitHub Actions task?
+-- New CI pipeline?
| +-- Single language? -> Minimal workflow with build + test
| +-- Multi-platform/version? -> Matrix strategy
| +-- Monorepo? -> Path-filtered triggers per project
+-- Reusing workflow logic?
| +-- Multi-job orchestration? -> Reusable workflow (workflow_call)
| +-- Reusable step sequence? -> Composite action
| +-- Complex logic with API calls? -> JavaScript action
+-- Choosing triggers?
| +-- See Trigger Decision Tree below
+-- Securing workflows?
| +-- Third-party actions? -> Pin to SHA
| +-- Fork PRs? -> Use pull_request (NOT pull_request_target)
| +-- Production deploy? -> Environment protection + approval gates
+-- Debugging failures?
+-- Workflow not triggering? -> Check branch/path filters
+-- Permission denied? -> Add explicit permissions block
+-- Cache miss? -> Verify lockfile and cache key
Table of Contents
- Trigger Decision Tree
- Directory Structure
- Minimal Workflow Example
- Common Actions Quick-Reference
- Core Concepts (with Progressive Disclosure)
- Security Best Practices read in full
- Troubleshooting
- Best Practices Summary
Trigger Decision Tree
Use this to choose the right event trigger for your workflow:
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/actions-marketplace-examples.md 2.1 KB
- references/devops-pipeline-template.yml 2.3 KB
- references/jobs-and-steps-patterns.md 2.0 KB
- references/reusable-workflows-and-actions.md 4.6 KB
- references/secrets-variables-matrix.md 2.0 KB
- references/workflow-syntax-reference.md 3.1 KB
- scripts/validate-workflows.ps1 5.2 KB runs code
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 Changed 660148bd4319
- 1mo ago First seen · 381 lines · 52 tokens per session scan A 521c8d95bd20
github-actions-workflows is a skill published in the GitHub repository jnPiyush/AgentX (16 stars, last pushed 3d ago), licensed Apache-2.0. It adds 52 tokens to every session and 3,602 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.
deployment-engineer
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization.…
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.