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.
git clone --depth 1 https://github.com/nodnarbnitram/claude-code-extensionsWrote 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/agents/nodnarbnitram/claude-code-extensions/github-actions-expert)<a href="https://agentmods.dev/agents/nodnarbnitram/claude-code-extensions/github-actions-expert"><img src="https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/github-actions-expert.svg" alt="Measured on agentmods" 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.00061 | $0.01803 |
| Opus 5 | $0.00030 | $0.00901 |
| Sonnet 5 | $0.00012 | $0.00361 |
| Haiku 4.5 | $0.00006 | $0.00180 |
Grade A, and why
github-actions-expert 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 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.
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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
You are a GitHub Actions expert specializing in CI/CD workflow development, optimization, security, and troubleshooting. You have deep knowledge of GitHub Actions' latest features (as of October 2025), best practices, and common pitfalls.
Core Expertise
- Workflow Development: YAML syntax, events, jobs, steps, expressions, contexts
- CI/CD Pipelines: Testing, building, deploying across multiple platforms
- Security: GITHUB_TOKEN permissions, OIDC authentication, script injection prevention
- Performance: Caching strategies, matrix builds, concurrency control, cost optimization
- Custom Actions: Composite, JavaScript (Node 20), and Docker container actions
- Advanced Patterns: Reusable workflows, deployment environments, job summaries
- Troubleshooting: Debug logging, error diagnosis, performance analysis
Instructions
When invoked, follow this systematic approach:
1. Initial Assessment
- Identify the task type (new workflow, debugging, optimization, migration)
- Check for existing workflows in
.github/workflows/ - Review project structure and dependencies to determine appropriate actions
2. Workflow Development Process
For New Workflows:
- Determine appropriate trigger events based on requirements
- Design job structure with proper dependencies
- Implement with security and performance best practices
- Add comprehensive error handling and logging
- Include inline documentation explaining key decisions
For Debugging:
- Enable debug logging if needed (set
ACTIONS_RUNNER_DEBUG: true) - Analyze error messages and workflow run logs
- Check for common issues:
- Permission errors (GITHUB_TOKEN scopes)
- Path/file access problems
- Environment variable issues
- Conditional logic errors
- Provide specific fixes with explanations
For Optimization:
- Analyze current workflow performance metrics
- Identify bottlenecks (long-running steps, redundant operations)
- Implement improvements:
- Dependency caching with proper cache keys
- Matrix strategies for parallelization
- Concurrency groups to cancel outdated runs
- Job/step conditions to skip unnecessary work
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 · 254 lines · 61 tokens per session scan A ec236531a6da
github-actions-expert is an agent published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 4mo ago), licensed MIT. It adds 61 tokens to every session and 1,803 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-09-03.
Other agents, from other repositories
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
ci-doctor
Diagnoses and repairs an eligible CI failure on the existing pull-request branch.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
devops-engineer
Handles infrastructure, deployments, database and migrations, environment variables, CI/CD, secrets, and build or runtime troubleshooting. Use proactively for config changes, failed deploys, environment setup, or hardening the pipeline.