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.
npx skills add ulises-jeremias/agent-toolkit --skill megalintergit clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitWrote 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/skills/ulises-jeremias/agent-toolkit/megalinter)<a href="https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/megalinter"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/megalinter/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/skills/ulises-jeremias/agent-toolkit/megalinter"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/megalinter.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.00101 | $0.01178 |
| Opus 5 | $0.00051 | $0.00589 |
| Sonnet 5 | $0.00020 | $0.00236 |
| Haiku 4.5 | $0.00010 | $0.00118 |
Grade A, and why
megalinter 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MegaLinter orchestrator
You orchestrate MegaLinter on this repository. MegaLinter is a mega-linter aggregating 100+ linters, running as a Docker image (locally via npx mega-linter-runner) or as a CI job.
Workflow
- Detect repository state:
- No
.mega-linter.ymland no MegaLinter CI workflow file → run themegalinter-setupskill first. - Configuration present → go to step 2.
- No
- Collect errors with the
megalinter-checkskill:- If a MegaLinter CI job is currently running or just failed for the current branch/PR → use its watch mode.
- Otherwise → use its local mode (requires a container engine — docker or podman; the skill handles asking the user to install/start one if missing). Local runs are resource-consuming (MegaLinter is Docker-based, needs a good computer configuration and a good internet connection, and can download images of several GB), so when a CI run is also achievable (the repository has a MegaLinter CI workflow — e.g. by pushing the branch or opening a PR), using CI is usually recommended: ask the user which one they want (structured question when your platform has one, CI first/recommended) instead of defaulting to local.
- If errors were found, run the
megalinter-fixskill with the collected error list. - Re-check: after fixes, run
megalinter-checkagain — in local mode, prefer its targeted re-check (parallel standalone linter runs restricted to previously-failing linters and fixed files). - Repeat steps 3-4 at most 3 times. If errors remain after 3 iterations, stop and report the remaining errors with your recommendation (fix manually, disable rules, or disable linters).
- Performance: if
megalinter-checkreportedslow_linters(even on a green run), relay its performance suggestions to the user at the end of the loop — speed wins are proposed, never applied without agreement.
Rules
- Never commit or push on the default branch (
main/master): create a branch likemegalinter/fix-<topic>first. - Ask the user before disabling any linter or rule, and before pushing commits.
- Keep the user informed with a short status after each phase (errors found, fixes applied, remaining).
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.
- 6d ago First seen · 79 lines · 101 tokens per session scan A c67fbb4cfc07
megalinter is a skill published in the GitHub repository ulises-jeremias/agent-toolkit (16 stars, last pushed today), licensed MIT. It adds 101 tokens to every session and 1,178 once invoked, about $0.0005 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-09-04.
Other skills, from other repositories
ci-debug-loop
Watch a GitHub Actions CI run, diagnose failures from logs, apply fixes, re-push, and repeat until green or escalate. Use when CI is failing and the user wants to debug and fix it iteratively, or says "fix CI", "debug the build", or similar.
GitHub CI Fix Debugging
Debug and fix failing GitHub PR checks by inspecting GitHub Actions logs, summarizing failure context, drafting fix plans, and implementing fixes after approval.
skillnote-doctor
A diagnostic tool for OpenClaw agents -- checks skill registry connectivity, AGENTS.md setup, config file validity, and installed skill health. Use when your setup seems broken, skills aren't loading, or you want to audit your agent's configuration.
chatcrystal-debug-recall
Recall ChatCrystal memories for debugging tasks involving failing tests, compiler errors, runtime exceptions, dependency issues, environment breakage, or performance regressions. Use when historical root causes, fixes, or pitfalls may accelerate diagnosis before proposing a fix.
github-actions-debugger
Debug and monitor GitHub Actions workflow runs. Check run status, view failed job logs, and troubleshoot CI failures. Use this when the user needs to investigate GitHub Actions failures, inspect job output, or identify the root cause of a broken workflow run.
gitlab-pipeline-debugger
Debug and monitor GitLab CI/CD pipelines for merge requests. Check pipeline status, view job logs, and troubleshoot CI failures. Use this when the user needs to investigate GitLab CI pipeline issues, check job statuses, or view specific job logs.