setup

A read-only check for the actionlint workflow-checking hook's prerequisites and settings. It examines what the hook actually needs and reports whether those requirements are available.

In plain words
What is it for?
Use it to verify actionlint setup, inspect the hook's runtime requirements, and receive remediation guidance without changing the repository or installing packages.
Why use it?
A hook may appear configured but silently fail when a required command or setting is missing. This check helps distinguish a working setup from one that needs attention.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/melodic-software/claude-code-plugins/setup
Any agent
npx skills add melodic-software/claude-code-plugins --skill setup
Clone the repo
git clone --depth 1 https://github.com/melodic-software/claude-code-plugins

Made for: Claude Code, Codex.

Per session 73 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,923 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00073 $0.01923
Opus 5 $0.00036 $0.00962
Sonnet 5 $0.00015 $0.00385
Haiku 4.5 $0.00007 $0.00192

Measured 2d ago against content hash a59ce11cace0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

setup 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 2d 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.

plugins/actionlint/skills/setup/SKILL.md · 122 lines

How it starts

The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Purpose

Thin check-centric setup per the uniform setup contract (docs/PLUGIN-PHILOSOPHY.md "Setup is explicit and repeatable" in the marketplace repository): check inspects and reports, apply resolves. This plugin owns no consumer-project configuration. actionlint auto-discovers its own optional config from the repository, and the tunables are the native userConfig options (the actionlint_enabled toggle and stdin_read_timeout). Every prerequisite is a PATH binary the plugin never bundles, and the plugin never installs system packages, so apply is guidance-only with no write path. It never modifies the repository, user settings, or the plugin cache.

Action routing: no argument or check runs the check; apply runs the check first, then offers remediation guidance. Both are non-interactive. Never prompt when the action is given.

check (read-only)

The hook script (${CLAUDE_PLUGIN_ROOT}/hooks/actionlint-check.sh) is the single source of truth for what it requires and how it resolves things.

Read it first. Probe what it actually does, don't recite this file. Then run each probe via Bash and report a PASS/FAIL/INFO table with one remediation line per FAIL. Do not modify anything.

When the plugin's toggle is disabled, every prerequisite absence downgrades from FAIL to INFO. The hook exits through its enabled-gate before probing anything, so a deliberately disabled plugin is not broken. Report the probes informationally and note that re-enabling restores the FAIL semantics.

  1. Bash version. Check against the hook's documented floor (README Requirements), noting any features the hook degrades without (for example telemetry's EPOCHREALTIME, a Bash 5.0+ builtin).
  2. jq. command -v jq. FAIL if absent: the hook then skips with a visible once-per-session notice instead of linting.
  3. actionlint. command -v actionlint. FAIL if absent: the hook skips workflow lint with a visible once-per-session notice (it ships no binary of its own).
  4. actionlint config. INFO: actionlint auto-discovers an optional .github/actionlint.yaml from the repository when present. It is not required. actionlint runs with its built-in defaults without one. Report whether one exists for the reader's awareness; its absence is not a FAIL.
  5. Hook toggle. Report the effective actionlint_enabled value: ${user_config.actionlint_enabled} (unexpanded or empty means default true; any value other than true disables the hook). 5b. Stdin read timeout. INFO: report the effective stdin_read_timeout value: ${user_config.stdin_read_timeout} (unexpanded or empty means default 2 seconds, minimum 1). It is an IDLE bound. Any byte arriving resets it, so it fires only once the pipe has gone silent for that long, at which point this hook fails open. A value read -t will not accept, or 0, falls back to the default.
  6. Hook registration. INFO: confirm the plugin is enabled for this project (/plugin → Installed) rather than parsing settings files.

Read the full file on GitHub · 122 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 2d ago First seen · 122 lines · 73 tokens per session scan A a59ce11cace0

Subscribe to this mod's changes

setup is a skill published in the GitHub repository melodic-software/claude-code-plugins (12 stars, last pushed 2d ago), licensed MIT. It adds 73 tokens to every session and 1,923 once invoked, about $0.0004 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-08-30.

Related

Other skills, from other repositories

deep-research

Conducts iterative deep research on any topic using web search, progressive exploration, and structured synthesis. Use when asked for comprehensive research, deep investigation, thorough analysis, or multi-source exploration of any topic. Triggers: research, investigate, deep dive, comprehensive analysis, explore…

jimmc414/claude-code-plugin-marketplace · 64 tokens

error-ux

Principles and patterns for writing error messages that help users recover. Use when auditing, writing, or improving error messages in code. Triggers: error messages, user experience, error handling, exception messages, validation errors.

jimmc414/claude-code-plugin-marketplace · 48 tokens

adversarial-patterns

Library of realistic adversarial attack vectors and anti-patterns to avoid. Contains examples of valid attacks and subtle gaming patterns to reject.

jimmc414/claude-code-plugin-marketplace · 32 tokens

documentation-testing

Provides heuristics for identifying incomplete or broken documentation. Use when validating README setup instructions, testing onboarding flows, or auditing documentation quality. Triggers: docs, readme, onboarding, setup validation, documentation audit.

jimmc414/claude-code-plugin-marketplace · 45 tokens

adversarial-analysis

Analyze code to identify explicit contracts, implicit usage patterns, and realistic boundary conditions. Contains concrete formulas for calculating input realism limits. Use before generating adversarial tests.

jimmc414/claude-code-plugin-marketplace · 37 tokens

propagate-then-search

For constraint problems: eliminate impossibilities before guessing, reduce search space through inference, fail fast on contradictions.

jimmc414/claude-code-plugin-marketplace · 27 tokens