eol-normalizer

eol-normalizer is a plugin for Claude Code from melodic-software/claude-code-plugins. Its token cost is not measured, scanned A, original, MIT.

A file-edit hook that changes a file's line endings to match the setting in its Git attributes file. It supports both LF and CRLF endings and only gives advice when it cannot apply the change.

In plain words
What is it for?
It helps keep edited files consistent with a repository's .gitattributes rules, especially when developers use different operating systems.
Why use it?
It prevents line-ending changes from creating noisy diffs or causing files to use the wrong format for a project.

Plugin for Claude Code

Written for Claude Code: a Claude Code plugin manifest.

Good fit It helps keep edited files consistent with a repository's .gitattributes rules, especially when developers use different operating systems.

Compare 6 plugins from other repositories ↓
Install in Claude Code
/plugin marketplace add melodic-software/claude-code-plugins
/plugin install eol-normalizer
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/melodic-software/claude-code-plugins

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 eol-normalizer

README.md
[![agentmods](https://agentmods.dev/badge/plugins/melodic-software/claude-code-plugins/eol-normalizer/github.svg)](https://agentmods.dev/plugins/melodic-software/claude-code-plugins/eol-normalizer)
Your own site
<a href="https://agentmods.dev/plugins/melodic-software/claude-code-plugins/eol-normalizer"><img src="https://agentmods.dev/badge/plugins/melodic-software/claude-code-plugins/eol-normalizer/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 eol-normalizer

Your own site · 80×15
<a href="https://agentmods.dev/plugins/melodic-software/claude-code-plugins/eol-normalizer"><img src="https://agentmods.dev/badge/plugins/melodic-software/claude-code-plugins/eol-normalizer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
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.
Security

Grade A, and why

eol-normalizer 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/eol-normalizer/.claude-plugin/plugin.json · 34 lines

What it actually says

{
  "name": "eol-normalizer",
  "version": "0.9.13",
  "description": "Normalize a written file's working-tree line endings to its .gitattributes eol value on edit: symmetric CRLF/LF driven by git check-attr, advisory and never blocking.",
  "author": {
    "name": "Melodic Software",
    "email": "[email protected]"
  },
  "license": "MIT",
  "keywords": [
    "eol",
    "line-endings",
    "crlf",
    "lf",
    "gitattributes",
    "normalizer",
    "hook"
  ],
  "userConfig": {
    "eol_normalizer_enabled": {
      "type": "boolean",
      "title": "Normalize line endings on edit",
      "description": "Normalize a written file's line endings to its .gitattributes eol value",
      "default": true
    },
    "eol_normalizer_lint_gitignored": {
      "type": "boolean",
      "title": "Act on files git ignores",
      "description": "By default the hook leaves a file the repository gitignores alone: it is not normalized, since a rewrite of an ignored file has no git checkout to undo it. Set true to act on gitignored files too. A tracked file that matches an ignore pattern is always in scope.",
      "default": false
    }
  }
}
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 Changed 475236ef8182
  2. 4d ago Changed f9915f62387d
  3. 8d ago Changed bbfba1dfa85c
  4. 11d ago Changed caf12c28bb00
  5. 12d ago Changed · -1 lines 3ab73e631476
  6. 13d ago Changed ba58ef6291b3
  7. 14d ago Changed c93032324a88
  8. 15d ago Changed e25be76a67a8
  9. 16d ago Changed 0c2390cb1004
  10. 17d ago First seen · 35 lines scan A 112128b484e7

Subscribe to this mod's changes

eol-normalizer is a plugin published in the GitHub repository melodic-software/claude-code-plugins (25 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-03.