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/jenreh/appkit/github-actions-cicdnpx skills add jenreh/appkit --skill github-actions-cicdgit clone --depth 1 https://github.com/jenreh/appkitWhat 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.00098 | $0.01421 |
| Opus 5 | $0.00049 | $0.00711 |
| Sonnet 5 | $0.00020 | $0.00284 |
| Haiku 4.5 | $0.00010 | $0.00142 |
Grade A, and why
github-actions-cicd 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 2d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Actions CI/CD Skill
When to Use
- Creating a new CI/CD workflow from scratch
- Auditing an existing workflow for security, performance, or correctness
- Debugging a failing or misbehaving workflow
- Designing deployment strategies (rolling, blue/green, canary)
- Configuring secrets, OIDC, or environment protections
Mode: Create
1. Gather Requirements
Ask (or infer from context):
- Trigger events:
push,pull_request,workflow_dispatch,schedule? - Language/runtime (Python, Node.js, etc.) — determines setup actions and cache paths
- Test stages needed: unit, integration, E2E?
- Deployment target: cloud provider, registry, k8s?
- Environments: staging + production with manual approval gates?
2. Scaffold Structure
name: <Descriptive Name>
on: ...
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
permissions:
contents: read # least privilege default
jobs:
lint: ...
test: ...
build: ...
deploy: ...
3. Apply Checklist per Job
-
runs-on: ubuntu-latest(or justified alternative) -
actions/checkout@v4withfetch-depth: 1 - Cache keyed on
hashFiles('**/lockfile')withrestore-keysfallback - All
uses:pinned to full commit SHA or major version tag (@v4, not@main) -
timeout-minutesset for long-running jobs - Secrets via
${{ secrets.NAME }}— never hardcoded
4. Security Gates
- Least-privilege
permissionsblock at workflow + override at job level - OIDC for cloud auth (prefer over long-lived keys)
dependency-review-actionon PRs targeting default branch- CodeQL or Bandit for SAST on push/PR
5. Deployment Configuration
- Use
environment:blocks with protection rules for staging/prod - Manual approval required for
productionenvironment - Store rollback artifact version as job output; document rollback command in workflow comment
Mode: Review (Audit Checklist)
Run through these checks on any existing workflow:
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.
- 2d ago First seen · 172 lines · 98 tokens per session scan A 22056bc20051
github-actions-cicd is a skill published in the GitHub repository jenreh/appkit (4 stars, last pushed 6d ago), licensed MIT. It adds 98 tokens to every session and 1,421 once invoked, about $0.0005 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
ima2
Use the ima2-gen CLI/server to generate, edit, inspect, and manage local AI image generation jobs.
videoagent-image-studio
Tired of juggling 8 API keys? This skill gives you one-command access to Midjourney, Flux, Ideogram, and more, with zero setup. Use when you want to generate any image without worrying about API keys.
motion
How an agent turns a character mesh into a usable animated FBX — and how to judge whether the result is shippable.
image
Use this Skill when a game plan needs a single-subject concept image, a character reference cleaned for image-to-3D, or a front-facing transparent T-pose image for downstream character reconstruction. T-pose generation is an image-generation and image-editing task; it is not a separate asset category.
comfyui-skill-openclaw
Run registered ComfyUI workflows through the fast comfyui-skill CLI, and use the official local Comfy MCP for live template, node, model, validation, and orchestration capabilities. Use this Skill when: (1) The user requests to "generate an image", "draw a picture", or "execute a ComfyUI workflow". (2) The user has…
audio
Use this Skill when a game plan requires dialogue, voice lines, sound effects, foley, ambience, or other offline WAV assets. This is asset generation, not a runtime audio-playback contract; use the selected engine context after an asset has passed review.