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 commands/nitinjain999/platform-skills/github-actionsgit clone --depth 1 https://github.com/nitinjain999/platform-skillsWhat 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.00040 | $0.03243 |
| Opus 5 | $0.00020 | $0.01622 |
| Sonnet 5 | $0.00008 | $0.00649 |
| Haiku 4.5 | $0.00004 | $0.00324 |
Grade A, and why
github-actions scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
TOKEN=$(curl -sSfL -H "Authorization: bearer $ACTIONS_ID_TOKEN_REQUEST_TOKEN" \ 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 Command
Structured guidance for designing, hardening, reviewing, and debugging GitHub Actions workflows.
Activation
/platform-skills:github-actions design # reusable workflow or job graph design
/platform-skills:github-actions security # OIDC, SHA pinning, token scoping, secrets hygiene
/platform-skills:github-actions review # production-readiness checklist for an existing workflow
/platform-skills:github-actions debug # diagnose a failing workflow or job
Interactive Wizard (fires when no mode is provided)
When invoked with no arguments, ask before proceeding:
Q1 — Mode?
What do you need?
1. design — reusable workflow, job graph, promotion pipeline
2. security — OIDC federation, SHA pinning, token scoping, secret hygiene
3. review — production-readiness checklist for an existing workflow file
4. debug — job failure, permission error, OIDC rejection, missing context
Enter 1–4 or mode name:
Q2 — Context (after mode selected):
- design:
Describe what the workflow should do — validate, build, promote, deploy? - security:
Paste the workflow file or describe the auth pattern you are using. - review:
Paste the workflow file or provide the path. - debug:
Paste the error output or describe the failure symptom.
Mode: design
Triggers: design, build workflow, create pipeline, reusable workflow, job graph, promote, deploy flow
Read references/github-actions.md before responding.
Step 1 — Classify the workflow type
| Type | When to use |
|---|---|
Reusable workflow (workflow_call) |
Same job sequence needed across multiple repos or environments |
| Composite action | Same step sequence needed within job graphs — use /platform-skills:composite-actions |
| Standard workflow | One-off or repo-specific, not shared |
Step 2 — Apply the canonical job pattern
Every workflow should follow this job order:
validate → build → [test] → promote → [deploy]
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.
- 3d ago First seen · 381 lines · 40 tokens per session scan A a664a52913e3
github-actions is a command published in the GitHub repository nitinjain999/platform-skills (40 stars, last pushed 3d ago), licensed Apache-2.0. It adds 40 tokens to every session and 3,243 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
setup-ci
Tu es un DevOps Engineer expert. Tu dois configurer un pipeline CI/CD adapté aux technologies du projet, en suivant les bonnes pratiques.
bootstrap
Scaffold test, lint, and CI infrastructure for projects that lack it.
sm-sail
Command "sm-sail" from ScienceIsNeato/slop-mop, covering /sm-sail — drive a pr to green, autonomously, the loop, when sail parks on review threads, when to stop before "pr ready" — only two reasons and expect convergence, not one pass.
ci-status
Real-time GitHub Actions workflow status and recent runs.
sm-buff
You usually don't run buff directly — run sm sail. sm sail drives the whole PR to green and calls buff watch / triage for you, stopping only when it needs you to act (see /sm-sail). Reach for sm buff here only for surgical work: inspecting a specific failure, or resolving a single review thread when sail has parked on…
ghactions
Validate that GitHub Actions workflows for the latest push of yandex-wiki-search-mcp are passing.