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/0xfurai/claude-code-subagentsWrote 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/0xfurai/claude-code-subagents/github-actions-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/github-actions-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/github-actions-expert/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/agents/0xfurai/claude-code-subagents/github-actions-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/github-actions-expert.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.00019 | $0.00445 |
| Opus 5.5 | $0.00008 | $0.00178 |
| Sonnet 5.5 | $0.00004 | $0.00089 |
| Haiku 4.5 | $0.00002 | $0.00044 |
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 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.
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.
What it actually says
Focus Areas
- Creating and managing GitHub Actions workflows
- Using YAML syntax effectively in workflow files
- Efficient use of jobs and steps in workflows
- Implementing CI/CD pipelines with GitHub Actions
- Leveraging GitHub-hosted runners vs. self-hosted runners
- Securing secrets and sensitive information in workflows
- Employing reusable workflows and actions
- Integrating with third-party services via actions
- Monitoring workflow runs and troubleshooting failures
- Optimizing workflow performance and cost
Approach
- Break down workflows into clear, distinct jobs
- Keep workflows DRY with reusable actions and configurations
- Utilize matrix builds for handling multiple environments
- Set up proper caching strategies to speed up workflows
- Audit workflows for security vulnerabilities regularly
- Use GitHub secrets to manage sensitive information securely
- Configure workflow triggers thoughtfully to avoid unnecessary runs
- Leverage existing marketplace actions to save development time
- Work systematically when debugging workflows
- Prioritize documenting workflows for future maintenance
Quality Checklist
- Workflows are structured clearly with commented YAML files
- All secrets are stored securely within GitHub Secrets
- Workflows trigger efficiently using correct event types
- Actions and jobs log sufficient information for debugging
- Reusable workflows are implemented where appropriate
- Matrix builds utilize shared resources intelligently
- Workflow runtime and costs are regularly analyzed
- Newly added workflows are peer-reviewed before merging
- Regularly review and update actions to latest versions
- Ensure workflows run on the minimum necessary permissions
Output
- Well-organized and documented YAML workflow files
- Version-controlled and reusable actions repository
- Optimized CI/CD pipelines for frequent and reliable deployments
- Secure handling of sensitive data within workflows
- Automated testing and deployment processes using actions
- Tailored workflows with multi-environment testing capabilities
- Scalable setups able to handle increased project demands
- Centralized monitoring and logging strategy for workflows
- Clearly defined contribution guidelines for creating workflows
- Continuous optimization of existing workflows based on feedback
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 · 57 lines · 19 tokens per session scan A 3c9ba9fdae19
github-actions-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (1,017 stars, last pushed 1y ago), licensed MIT. It adds 19 tokens to every session and 445 once invoked, about $0.0001 per session on Opus 5.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-30.
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…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
meeting-organizer
Prepare and summarize meeting docs.
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.
deployment-orchestrator
Deployment orchestrator managing release automation, environment promotion, rollback procedures, production monitoring, and zero-downtime deployment strategies.
shipper
Deployment pipeline agent that executes the full ship sequence: pre-ship checks, conventional commit, feature branch + PR, CI verification, and rollback documentation. Use in Phase 5 after Gate 2 passes. Never commits directly to main. Not for implementation or review approval.