wiswa-mcp: Agent for Claude Code

.claude/agents/workflow-shellcheck.md

workflow-shellcheck is an agent for Claude Code from Tatsh/wiswa-mcp. It costs 28 tokens per session (541 once invoked), scanned A, original, MIT.

An agent that checks Bash scripts embedded in GitHub Actions workflow files. GitHub Actions runs automated tasks such as tests and deployments when code changes.

In plain words
What is it for?
Use it after editing workflow scripts to extract Bash commands, run ShellCheck, fix reported issues, and reformat the YAML.
Why use it?
It catches shell-script problems that may make automated workflows fail or behave unexpectedly. It can apply ShellCheck’s suggested corrections.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

This is Tatsh/wiswa-mcp's own configuration. It tells Claude Code how to work on wiswa-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything wiswa-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Tatsh/wiswa-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Tatsh/wiswa-mcp/master/.claude/agents/workflow-shellcheck.md
Clone the repo
git clone --depth 1 https://github.com/Tatsh/wiswa-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for workflow-shellcheck

README.md
[![agentmods](https://agentmods.dev/badge/agents/tatsh/wiswa-mcp/workflow-shellcheck/github.svg)](https://agentmods.dev/agents/tatsh/wiswa-mcp/workflow-shellcheck)
Your own site
<a href="https://agentmods.dev/agents/tatsh/wiswa-mcp/workflow-shellcheck"><img src="https://agentmods.dev/badge/agents/tatsh/wiswa-mcp/workflow-shellcheck/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.

agentmods 80×15 button for workflow-shellcheck

Your own site · 80×15
<a href="https://agentmods.dev/agents/tatsh/wiswa-mcp/workflow-shellcheck"><img src="https://agentmods.dev/badge/agents/tatsh/wiswa-mcp/workflow-shellcheck.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 541 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.00541
Opus 5.5 $0.00011 $0.00216
Sonnet 5.5 $0.00006 $0.00108
Haiku 4.5 $0.00003 $0.00054

Measured 2mo ago against content hash 851cee70b7a0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

workflow-shellcheck 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 2mo 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.

.claude/agents/workflow-shellcheck.md · 50 lines

What it actually says

Workflow ShellCheck Agent

Extracts embedded Bash scripts from GitHub Actions workflow files, runs ShellCheck, and applies fixes.

Role

You lint and fix Bash scripts embedded in GitHub Actions workflow YAML files using ShellCheck.

Workflow

  1. Read each workflow file in .github/workflows/*.yml.
  2. For each step with shell: 'bash' (explicit or implicit - run: defaults to bash on Linux): a. Skip steps with shell: 'pwsh' or shell: 'powershell'. b. Extract the run: value. c. Write it to a temporary .sh file with #!/usr/bin/env bash as the first line. d. Run shellcheck -f diff <tempfile> to get a diff of suggested fixes. e. If ShellCheck reports issues, apply the fixes to the original run: block in the workflow YAML. f. Clean up the temporary file.
  3. Run yarn format to re-format the YAML after edits.

ShellCheck considerations

  • Use shellcheck -s bash to specify bash dialect.
  • Common issues in GitHub Actions scripts:
    • SC2086: Double-quote to prevent word splitting ($var → "$var").
    • SC2046: Quote command substitution ($(cmd) → "$(cmd)").
    • SC2034: Unused variables (may be intentional for GitHub Actions $GITHUB_ENV exports).
    • SC2154: Referenced but not assigned (may come from ${{ }} template expressions).
  • GitHub Actions template expressions (${{ ... }}) are not valid bash. ShellCheck will flag them. Ignore SC1091 and SC2154 warnings that are caused by template expressions.
  • Add # shellcheck disable=SC2154 at the top of extracted scripts that use ${{ }} expressions if needed, but do not add these to the actual workflow YAML.

Rules

  • Only fix real Bash issues, not false positives from GitHub Actions template syntax.
  • Do not change pwsh or powershell scripts.
  • Preserve the original indentation of the YAML run: block.
  • If a script is a single-line run: (not a | block), only apply fixes that keep it on one line.
Changes

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.

  1. 2mo ago First seen · 50 lines · 28 tokens per session scan A 851cee70b7a0

Subscribe to this mod's changes

workflow-shellcheck is an agent published in the GitHub repository Tatsh/wiswa-mcp (0 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 541 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.

Related

workflow-shellcheck compared with agents from other repositories

workflow-shellcheck next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
workflow-shellcheckTatsh/wiswa-mcpAgent0yesterdayMITA28Claude Code
kingdee-qa-engineerWaHaiLong/KingdeeMCPAgent13612d agoMITA49Claude Code
ci-doctortheam/facilityAgent87yesterdayApache-2.0A19Claude Code
staff-infrastructureATTCKDigital/smithAgent55yesterdayMITA54Claude Code
qahamc/blastproofAgent11todayMITA52Claude Code
retrospectiverjmurillo/ai-agentsAgent49yesterdayMITA0Claude Code
orc-ci-investigatorHigorAlves/orcAgent7yesterdayMITA67Claude Code