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 kolodkin/devpowers --skill action-rungit clone --depth 1 https://github.com/kolodkin/devpowersWrote 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/kolodkin/devpowers/action-run)<a href="https://agentmods.dev/skills/kolodkin/devpowers/action-run"><img src="https://agentmods.dev/badge/skills/kolodkin/devpowers/action-run/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/kolodkin/devpowers/action-run"><img src="https://agentmods.dev/badge/skills/kolodkin/devpowers/action-run.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.00074 | $0.02195 |
| Opus 5.5 | $0.00030 | $0.00878 |
| Sonnet 5.5 | $0.00015 | $0.00439 |
| Haiku 4.5 | $0.00007 | $0.00219 |
Grade A, and why
action-run 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 1mo 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.
s=$(curl -fsSL \ How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Action Run Skill
Trigger any GitHub Actions workflow_dispatch workflow by name, gather required inputs, monitor it to completion, and fix failures automatically — driven through the GitHub MCP server's actions toolset (mcp__plugin_devpowers_github__actions_*, mcp__plugin_devpowers_github__get_job_logs), exactly the way /check-pr drives PR/CI status through mcp__plugin_devpowers_github__pull_request_read. No gh CLI.
Invocation Format
/action-run <workflow description> [key=value] [flag] ... [branch=<name>]
Examples:
/action-run hello
/action-run hello name=Mark shout
/action-run pypi publish tag=v0.0.8 pre-release
/action-run pypi publish tag=v0.0.8 branch=main
/action-run generate migration message="add users table"
Step 0 — Ensure the GitHub MCP actions toolset is available
This skill drives everything through the actions toolset of the github MCP server bundled with this plugin — its .mcp.json loads as mcp__plugin_devpowers_github__*, and the X-MCP-Toolsets: all header turns the actions tools on.
- If
mcp__plugin_devpowers_github__get_job_logs(and themcp__plugin_devpowers_github__actions_*tools) are visible in your tool list, proceed. - If they're missing, the plugin's bundled
githubMCP didn't connect — almost always becauseGH_TOKENisn't set (it authenticates withBearer ${GH_TOKEN}). Tell the user toexport GH_TOKEN=<pat>(a long-lived PAT) and restart Claude Code (or run/reload-plugins), then re-invoke/action-run. Stop until the server loads.
Triggering workflow_dispatch needs a token with Actions: write (classic workflow scope / fine-grained Actions: write). A read-only token can list and inspect runs, but run_workflow will fail with 403.
Tool shape: the hosted server groups Actions operations into method-based tools — mcp__plugin_devpowers_github__actions_run_trigger (methods run_workflow, rerun_failed_jobs, rerun_workflow_run, cancel_workflow_run), mcp__plugin_devpowers_github__actions_list (list_workflows, list_workflow_runs, list_workflow_jobs), mcp__plugin_devpowers_github__actions_get (get_workflow_run), and the standalone mcp__plugin_devpowers_github__get_job_logs. Server versions may rename these or shift methods; map the intent below to whatever mcp__plugin_devpowers_github__* actions tools your session actually exposes, and read each tool's registered schema for exact filter/pagination parameters.
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.
- 1mo ago First seen · 134 lines · 74 tokens per session scan A cd183ed64b72
action-run is a skill published in the GitHub repository kolodkin/devpowers (2 stars, last pushed 2d ago), licensed MIT. It adds 74 tokens to every session and 2,195 once invoked, about $0.0003 per session on Opus 5.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-31.
Other skills, from other repositories
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.
deployment-engineer
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization.…