What is megalinter-watcher?

An agent that watches MegaLinter, a collection of code-quality checkers, while it runs in a CI pipeline.

Use it with GitHub Actions, GitLab CI, Azure Pipelines, or Bitbucket Pipelines to wait for a MegaLinter job and summarize its failures.

It keeps large CI logs out of the main conversation and returns only the lint errors and related tips.

megalinter-watcher — Agent for Claude Code by ulises-jeremias

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.

Clone the repo

git clone --depth 1 https://github.com/ulises-jeremias/agent-toolkit

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/ulises-jeremias/agent-toolkit/megalinter-watcher/github.svg)](https://agentmods.dev/agents/ulises-jeremias/agent-toolkit/megalinter-watcher)

Your own site

<a href="https://agentmods.dev/agents/ulises-jeremias/agent-toolkit/megalinter-watcher"><img src="https://agentmods.dev/badge/agents/ulises-jeremias/agent-toolkit/megalinter-watcher/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/ulises-jeremias/agent-toolkit/megalinter-watcher"><img src="https://agentmods.dev/badge/agents/ulises-jeremias/agent-toolkit/megalinter-watcher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 70 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,118 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.

Model	Per session	Once invoked
Fable 5.1	$0.00070	$0.01118
Opus 5.5	$0.00028	$0.00447
Sonnet 5.5	$0.00014	$0.00224
Haiku 4.5	$0.00007	$0.00112

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

Security

Grade A, and why

megalinter-watcher 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.

skills/quality/megalinter-setup/agents/megalinter-watcher.md · 68 lines

How it starts

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

You are a MegaLinter CI job watcher. Your job is to observe — not to fix.

What you do

Identify the CI provider from the git remote URL and CI config files, then find the MegaLinter job for the current branch/PR:
- GitHub: gh run list --branch <branch>, gh run view <run-id>, gh run view <run-id> --log-failed
- GitLab: glab ci list, glab ci status, glab ci trace <job-id>
- Azure DevOps: az pipelines runs list --branch <branch>, az pipelines runs show --id <run-id>; logs via az pipelines runs artifact or the logs REST endpoint
- Bitbucket: REST API GET /2.0/repositories/{workspace}/{repo}/pipelines/ and .../steps/{step}/log with $BITBUCKET_TOKEN or app password
If the job is still running, poll its status (wait 30-60 seconds between polls) until it completes.
Download the logs of the MegaLinter step only.
Parse the MegaLinter summary table and per-linter sections from the logs.
Extract the console tips from the same log: MegaLinter prints actionable advice that never reaches reports (performance warnings like ">300 .gitignored files... consider ADDITIONAL_EXCLUDED_DIRECTORIES" or "Heavy folders detected", flavor suggestions, [Activation] notices explaining why a linter did not run, deprecation notices, timeout kills). Grep the downloaded log with grep -E "⚠|WARNING|\[Activation\]|Heavy folders|To improve|[Ff]lavor|deprecat|Timed out|[Cc]onsider".
Detect whether MegaLinter pushed its own fixes onto the branch (repositories using APPLY_FIXES_MODE: commit). Read-only, no fetch side effects beyond updating remote refs:
```
BRANCH="$(git branch --show-current)"
git fetch origin "$BRANCH"
git log -1 --format='%h %s' "origin/$BRANCH"
```
The auto-fix commit subject is [MegaLinter] Apply linters fixes (repositories may customize it). Report it — do not act on it: the calling skill decides whether to amend and re-push.

What you return

A compact JSON object, nothing else:

Read the full file on GitHub · 68 lines

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.

1mo ago Changed · +14 lines 1d63f2a6e01d
1mo ago First seen · 54 lines · 70 tokens per session scan A 3c62222f9b20

Subscribe to this mod's changes

megalinter-watcher is an agent published in the GitHub repository ulises-jeremias/agent-toolkit (19 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 1,118 once invoked, about $0.0003 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-09-04.

CI and CD Claude Code Debugging DevOps and cloud agent-toolkit ai-agents ai-tools cursor github-copilot

performance-reviewer

Investigates iOS performance problems — scroll hitches, slow launch, memory growth, main-actor contention, over-invalidating SwiftUI views. Measures before concluding and never optimizes on suspicion. Read-only plus Bash — it reports findings with evidence and never edits the code it measures.

Nagarjuna2997/ios-agent-skill · 61 tokens

swift-debugger

Root-cause analysis for Swift/iOS failures — compiler errors, test failures, crashes, data races, SwiftUI views that do not update. Use when something is broken and the cause is not obvious. Reproduces first, then fixes, then proves the fix with real output.

Nagarjuna2997/ios-agent-skill · 61 tokens

swift-refactorer

Behavior-preserving Swift cleanups — extracting subviews, introducing protocol seams, replacing literals with design tokens, adding @MainActor isolation, removing duplication. Use for mechanical improvement with no behavior change. Proves behavior is unchanged by running the tests before and after.

Nagarjuna2997/ios-agent-skill · 57 tokens

megalinter-watcher