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/soulcodex/agentic/github-actions-workflownpx skills add soulcodex/agentic --skill github-actions-workflowgit clone --depth 1 https://github.com/soulcodex/agenticWhat 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.00072 | $0.01769 |
| Opus 5 | $0.00036 | $0.00885 |
| Sonnet 5 | $0.00014 | $0.00354 |
| Haiku 4.5 | $0.00007 | $0.00177 |
Grade A, and why
github-actions-workflow 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Actions Workflow Skill
Step 1 — Detect Project Type
Identify the runtime and package manager before scaffolding:
- Language (Go, TypeScript/Node, Python, PHP, …)
- Package manager (pnpm, npm, Go modules, uv, Composer)
- Test and lint commands (from
justfile,Makefile, orpackage.json) - Deploy targets (container registry, cloud provider, static host)
Step 2 — Scaffold .github/workflows/ci.yml
name: CI
on:
push:
branches: [main]
pull_request:
concurrency:
group: ci-${{ github.ref }}
cancel-in-progress: true
jobs:
lint:
name: Lint
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Set up runtime
uses: <runtime-setup-action> # e.g. actions/setup-go@v5
with:
<version-key>: <version> # e.g. go-version: "1.23"
- name: Cache dependencies
uses: actions/cache@v4
with:
path: <cache-path>
key: ${{ runner.os }}-<tool>-${{ hashFiles('<lockfile>') }}
- name: Install dependencies
run: <install-command>
- name: Lint
run: <lint-command>
test:
name: Test
runs-on: ubuntu-latest
needs: lint
steps:
- uses: actions/checkout@v4
- name: Set up runtime
uses: <runtime-setup-action>
with:
<version-key>: <version>
- name: Cache dependencies
uses: actions/cache@v4
with:
path: <cache-path>
key: ${{ runner.os }}-<tool>-${{ hashFiles('<lockfile>') }}
- name: Install dependencies
run: <install-command>
- name: Test
run: <test-command>
build:
name: Build
runs-on: ubuntu-latest
needs: test
steps:
- uses: actions/checkout@v4
- name: Build
run: <build-command>
Step 3 — Job Structure
| Job | Depends on | Purpose |
|---|---|---|
lint |
— | Fail fast on code quality issues |
test |
lint |
Run unit and integration tests |
build |
test |
Verify the artefact compiles/bundles |
deploy |
build |
Push to environment (conditionally) |
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 · 239 lines · 72 tokens per session scan A 8b1e67e44831
github-actions-workflow is a skill published in the GitHub repository soulcodex/agentic (10 stars, last pushed yesterday), licensed MIT. It adds 72 tokens to every session and 1,769 once invoked, about $0.0004 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
research-repository
Build a repository that makes findings findable, reusable, and cumulative across teams. Use when the same research keeps getting redone. For synthesising one study, use affinity-diagram.
survey-design
Design unbiased survey instruments — question wording, scales, and sampling — to measure attitudes at scale. Use when you need quantitative breadth. For behavioural experiments, use a-b-test-design (prototyping-testing).
localization-design
Design for multiple languages, writing directions, and cultural contexts — text expansion, RTL mirroring, and locale formats. Use when shipping beyond one locale. For the words themselves, use ux-writing (designer-toolkit).
design-negotiation
Advocate for design quality, scope, and timeline with partners and leadership using evidence and shared goals. Use in the conversation itself. For the commercial vocabulary behind it, use business-design (ux-strategy).
design-debt-audit
Inventory and prioritise accumulated design inconsistencies across a product. Use when drift has built up over time. For token coverage specifically use design-token-audit (designer-toolkit); for WCAG gaps use accessibility-audit (design-systems).
design-impact-reporting
Communicate design's contribution to business and user outcomes in stakeholder language. Use when reporting results upward. For choosing the metrics in the first place, use metrics-definition (ux-strategy).