Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/selvarajmurugesan90/ops-engineering-skillsnpx agentmods add skills/selvarajmurugesan90/ops-engineering-skills/github-actions-single-repo-workflowsWrote 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/selvarajmurugesan90/ops-engineering-skills/github-actions-single-repo-workflows)<a href="https://agentmods.dev/skills/selvarajmurugesan90/ops-engineering-skills/github-actions-single-repo-workflows"><img src="https://agentmods.dev/badge/skills/selvarajmurugesan90/ops-engineering-skills/github-actions-single-repo-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/selvarajmurugesan90/ops-engineering-skills/github-actions-single-repo-workflows"><img src="https://agentmods.dev/badge/skills/selvarajmurugesan90/ops-engineering-skills/github-actions-single-repo-workflows.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 7 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Agent Snooping · line 32 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 319 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 211 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 320 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00111 | $0.03133 |
| Opus 5 | $0.00056 | $0.01566 |
| Sonnet 5 | $0.00022 | $0.00627 |
| Haiku 4.5 | $0.00011 | $0.00313 |
Grade A, and why
github-actions-single-repo-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 10d 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 — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Actions Single-Repo Workflows
Purpose
Most repos' CI needs are served by workflow YAML that lives entirely
within that repo under .github/workflows/, defining its own triggers,
jobs, and steps. This skill covers the concrete GitHub Actions mechanics
for that single-repo case — trigger syntax (on:), job/step structure,
matrix builds, actions/cache, and composite actions defined locally in
.github/actions/ for within-repo reuse — as distinct from the
organization-wide reusable-workflow pattern covered in
github-actions-centralized-reusable-workflows.
Generic pipeline-design concepts (stage ordering, quality gates, caching
philosophy) are covered vendor-neutrally in
ci-cd-pipeline-design;
this skill focuses on GitHub Actions' actual YAML syntax and runner
behavior.
When to use
- A repository needs its first CI workflow, or an existing
.github/workflows/*.ymlfile is failing and needs debugging. - Adding a matrix build (multiple OS/language versions) or parallel test sharding within one workflow.
- Speeding up a slow workflow via
actions/cache,concurrencycancellation, or splitting a monolithic job into parallel jobs withneeds:. - Extracting duplicated step sequences within one repo's workflows into a
local composite action under
.github/actions/. - Deciding whether logic duplicated across multiple repos (not just within one) should become an org-level reusable workflow instead — see github-actions-centralized-reusable-workflows.
Prerequisites & environment
- GitHub Actions enabled on the repository (Settings → Actions → General).
- Runner availability: GitHub-hosted runners (
ubuntu-latest,windows-latest,macos-latest) require no setup; self-hosted runners need registration and their own OS/tooling patching (Settings → Actions → Runners). - Repo write/admin access to add workflow files and configure branch protection required-status-checks.
- Secrets already stored in Settings → Secrets and variables → Actions (repository or environment-scoped) — never hardcoded in the workflow YAML.
- Familiarity with YAML expression syntax (
${{ }}) and GitHub's built-in contexts (github.*,secrets.*,matrix.*,needs.*).
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.
- 10d ago First seen · 321 lines · 111 tokens per session scan A cd1c88e35f36
github-actions-single-repo-workflows is a skill published in the GitHub repository selvarajmurugesan90/ops-engineering-skills (38 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 111 tokens to every session and 3,133 once invoked, about $0.0006 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-30.
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…
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.
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…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
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.
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/.