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 KunanonJ/ai-skills-hub --skill github-actions-creatorgit clone --depth 1 https://github.com/KunanonJ/ai-skills-hubWrote 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/kunanonj/ai-skills-hub/github-actions-creator)<a href="https://agentmods.dev/skills/kunanonj/ai-skills-hub/github-actions-creator"><img src="https://agentmods.dev/badge/skills/kunanonj/ai-skills-hub/github-actions-creator/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/kunanonj/ai-skills-hub/github-actions-creator"><img src="https://agentmods.dev/badge/skills/kunanonj/ai-skills-hub/github-actions-creator.svg" alt="Reviewed on agentmods" width="80" 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.00058 | $0.02501 |
| Opus 5 | $0.00029 | $0.01251 |
| Sonnet 5 | $0.00012 | $0.00500 |
| Haiku 4.5 | $0.00006 | $0.00250 |
Grade A, and why
github-actions-creator 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 8d 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 — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Actions Creator
You are an expert at creating GitHub Actions workflows. When the user asks you to create a GitHub Action, follow this structured process to deliver a production-ready workflow file.
Workflow Creation Process
Step 1: Analyze the Project
Before writing any YAML, scan the project to understand the stack:
-
Check for language/framework indicators:
package.json→ Node.js (check for React, Next.js, Vue, Angular, Svelte, etc.)requirements.txt/pyproject.toml/setup.py→ Pythongo.mod→ GoCargo.toml→ Rustpom.xml/build.gradle→ Java/KotlinGemfile→ Rubycomposer.json→ PHPpubspec.yaml→ Dart/FlutterPackage.swift→ Swift*.csproj/*.sln→ .NET
-
Check for existing CI/CD:
.github/workflows/→ existing workflows (avoid conflicts)Dockerfile→ container builds availabledocker-compose.yml→ multi-service setupvercel.json/netlify.toml→ deployment targetsterraform//pulumi/→ infrastructure as code
-
Check for tooling:
.eslintrc*/eslint.config.*→ ESLint configuredprettier*→ Prettier configuredjest.config*/vitest.config*/pytest.ini→ test framework.env.example→ environment variables neededMakefile→ build commands available
Step 2: Ask Clarifying Questions (if needed)
If the user's request is ambiguous, ask ONE focused question. Common clarifications:
- "Create a CI pipeline" → "Should it run tests only, or also lint and type-check?"
- "Add deployment" → "Where does this deploy? (Vercel, AWS, GCP, Docker Hub, etc.)"
- "Set up tests" → "Should tests run on PR only, or also on push to main?"
If the intent is clear, skip this step and proceed.
Step 3: Generate the Workflow
Create the .github/workflows/{name}.yml file following these rules:
File Naming
- Use descriptive kebab-case names:
ci.yml,deploy-production.yml,release.yml - For simple CI:
ci.yml - For deployment:
deploy.ymlordeploy-{target}.yml - For scheduled tasks:
scheduled-{task}.yml
What ships with it
1 file 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.
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.
- 8d ago First seen · 303 lines · 58 tokens per session scan A abf9347f6af2
github-actions-creator is a skill published in the GitHub repository KunanonJ/ai-skills-hub (5 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 2,501 once invoked, about $0.0003 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
rust-crate-ci
Load before editing any Rust crate in this repo (currently runners/swarm-sandbox-runner). Covers the mandatory local validation gate, common rustfmt/clippy pitfalls, and Windows-specific Rust correctness patterns that CI enforces but are hard to catch locally without a Windows toolchain.
ci-failure-batching
Batch collection and fix protocol for CI failures. Triggered when any CI check fails on a PR. Prevents serial diagnose-fix-push cycles by collecting all failures before fixing.
ci-fix-monitor
Codex adapter for monitoring and fixing CI failures on opencode-swarm PRs. Use when diagnosing failed checks, fixing package-check (npm tarball) failures, resolving quality/lint/format errors, fixing macOS cross-platform file I/O failures, or watching a PR until all checks are green.
swarm-ci-monitor
Codex adapter for end-to-end CI monitoring of an already-reviewed PR in opencode-swarm. Use when the user wants the swarm to monitor a reviewed-and-approved PR's CI, research every failure exhaustively, fix end-to-end, iterate until green (max 5 cycles), then merge. Composes ci-fix-monitor for fix recipes.
tech-debt-ci-review
Codex adapter for deep technical-debt and CI-stability audits. Use when asked to find test theater, flaky tests, missing or mis-scoped tests, brittle CI/toolchain behavior, structural debt blocking green PRs, or a remediation order for opencode-swarm.
devops-cloud
DevOps, cloud infrastructure, and platform engineering. Use when working with AWS, GCP, Azure, Kubernetes, Terraform, CI/CD pipelines, or infrastructure as code.