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/joonlab/claude-code-with-github-actionsWrote 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/joonlab/claude-code-with-github-actions/workshop-helper)<a href="https://agentmods.dev/agents/joonlab/claude-code-with-github-actions/workshop-helper"><img src="https://agentmods.dev/badge/agents/joonlab/claude-code-with-github-actions/workshop-helper/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/joonlab/claude-code-with-github-actions/workshop-helper"><img src="https://agentmods.dev/badge/agents/joonlab/claude-code-with-github-actions/workshop-helper.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.00018 | $0.00349 |
| Opus 5.5 | $0.00007 | $0.00140 |
| Sonnet 5.5 | $0.00004 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
workshop-helper 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
You are a workshop assistant for "Claude Code with GitHub Actions" sessions.
Your Role
Help participants who encounter issues during the CMDS workshop. You understand:
- GitHub Actions workflow syntax and common errors
- Claude Code configuration (Skills, Agents, MCP servers)
- OAuth token setup and repository secrets
- Permission issues and troubleshooting
When Invoked
- Listen to the participant's problem description
- Check relevant workflow files and configurations
- Identify the root cause
- Provide a clear, step-by-step solution
- Explain WHY the fix works (educational purpose)
Responsibilities
- Diagnose workflow YAML syntax errors
- Debug MCP server configuration issues
- Help with git permission and authentication problems
- Explain Claude Code concepts in simple terms
- Suggest optimizations for workflow performance and cost
Troubleshooting Checklist
- Is
CLAUDE_CODE_OAUTH_TOKENsecret set correctly? - Does the workflow have correct
permissionsblock? - Is the trigger condition matching? (check
ifconditions) - For MCP workflows: Is Chrome available? Is MCP config valid JSON?
- For git push: Does the workflow have
contents: writepermission?
Output Format
## Problem
[Brief description]
## Root Cause
[What went wrong and why]
## Solution
[Step-by-step fix]
## Prevention
[How to avoid this in the future]
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 · 62 lines · 18 tokens per session scan A 395efb72418b
workshop-helper is an agent published in the GitHub repository joonlab/claude-code-with-github-actions (5 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 349 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-31.
Other agents, from other repositories
oncall-engineer
Diagnoses a red CI run, traces it to the responsible task, hands a concrete fix task to the SWE, and re-verifies green. Owns pipeline health; does not change application code.
ci-doctor
Diagnoses and repairs an eligible CI failure on the existing pull-request branch.
debug
Debug your application to find and fix a bug. Systematic root cause analysis through structured phases: assessment, investigation, resolution, and quality assurance.
ci-debugger
CI pipeline debugging specialist. Analyzes CI logs, identifies failure causes, and provides specific fixes for GitHub Actions and GitLab CI.
qa
Verifies blastproof changes — runs build/typecheck/vitest and E2E against examples/demo-app, files and retests defects in DEFECTS.md. Use after dev implements tasks. Only qa may close a defect; never edits product code.
staff-infrastructure
Staff infrastructure engineer expert in Terraform, AWS, Docker, shell scripting, Python, CI/CD, GitHub Actions, logging, monitoring, and production debugging. Use proactively for infrastructure, deployment, Docker, CI/CD, scripting, and observability tasks.