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/ofershap/mcp-server-github-actions/github-actions-managementnpx skills add ofershap/mcp-server-github-actions --skill github-actions-managementgit clone --depth 1 https://github.com/ofershap/mcp-server-github-actionsWhat 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.00054 | $0.00622 |
| Opus 5 | $0.00027 | $0.00311 |
| Sonnet 5 | $0.00011 | $0.00124 |
| Haiku 4.5 | $0.00005 | $0.00062 |
Grade A, and why
github-actions-management 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Actions Management via MCP
Use this skill when you need to check CI/CD status, read workflow logs, re-run failed jobs, or trigger deployments.
Available Tools
| Tool | What it does |
|---|---|
list_workflows |
List all workflow files in a repository |
list_runs |
List workflow runs (filter by workflow or status) |
get_run |
Get details of a specific workflow run |
get_run_logs |
Get the logs URL for a run (zip download) |
rerun_workflow |
Re-run an entire workflow run |
rerun_failed_jobs |
Re-run only the failed jobs from a run |
cancel_run |
Cancel an in-progress or queued run |
list_artifacts |
List artifacts produced by a workflow run |
trigger_workflow |
Trigger a workflow via workflow_dispatch |
Workflow
- Use
list_runswithownerandrepoto see recent runs and their status - For failed runs:
get_runfor details, then decide whether torerun_failed_jobsor investigate logs trigger_workflowrequires the workflow file name and a branch — the workflow must have aworkflow_dispatchtrigger
Key Patterns
- All tools require
ownerandrepoparameters (e.g.,owner: "ofershap",repo: "my-project") list_runssupportsstatusfilter: "completed", "in_progress", "queued", "failure", "success"rerun_failed_jobsis preferred overrerun_workflow; it is faster and cheapertrigger_workflowneedsworkflow_id(filename like "ci.yml") andref(branch name)
Error Scenarios
- 401/403 from GitHub:
GITHUB_TOKENmissing, expired, or lacks Actions scope on the repo - Run or workflow not found: double-check
owner,repo, and numeric run id fromlist_runs trigger_workflowrejected: workflow file lacksworkflow_dispatchor branchrefis wrongget_run_logsreturns a zip URL only: download and unzip outside the tool to read full log text
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 · 49 lines · 54 tokens per session scan A d9d6cb877d6a
github-actions-management is a skill published in the GitHub repository ofershap/mcp-server-github-actions (4 stars, last pushed 23d ago), licensed MIT. It adds 54 tokens to every session and 622 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
ci-cd-and-automation
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
ci-triage
Classify CI failures — distinguish clear regressions from infra flakes and security-test failures. Produces structured failure reports.
devops-infrastructure
Guides Docker, CI/CD pipelines, deployment strategies, infrastructure as code, and observability setup. Use when writing Dockerfiles, configuring GitHub Actions, planning deployments, setting up monitoring, or when asked about containers, pipelines, Terraform, or production infrastructure.
use-vercel-action
Wire amondnet/vercel-action into a GitHub Actions workflow to deploy Vercel projects from CI. Use when the user asks to deploy to Vercel from GitHub Actions, add Vercel preview deploys, post a Vercel preview URL on a PR, configure prebuilt Vercel deployments, set up alias domains for previews, create a GitHub…
devops/deployment-process
部署流程和CI/CD配置，确保安全可靠的部署.
tdd-configure-ci
Configures CI/CD pipelines to mechanically enforce CONSTRAINTS.md quality bars and Floor-Guard anti-cheat rules. (Optional Utility).