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 laurigates/claude-plugins --skill configure-gitattributesgit clone --depth 1 https://github.com/laurigates/claude-pluginsWrote 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/laurigates/claude-plugins/configure-gitattributes)<a href="https://agentmods.dev/skills/laurigates/claude-plugins/configure-gitattributes"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/configure-gitattributes/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/laurigates/claude-plugins/configure-gitattributes"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/configure-gitattributes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00045 | $0.01576 |
| Opus 5.5 | $0.00018 | $0.00630 |
| Sonnet 5.5 | $0.00009 | $0.00315 |
| Haiku 4.5 | $0.00005 | $0.00158 |
Grade A, and why
configure-gitattributes 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.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/configure:gitattributes
Audit or create a repo's .gitattributes, applying the three high-value
attributes — merge=union for append-only tables, linguist-generated for
build output, and LF normalization — while never applying merge=union to a
file it would corrupt. See .claude/rules/gitattributes.md for the convention.
When to Use This Skill
| Use this skill when... | Use another approach when... |
|---|---|
A repo has no .gitattributes and wants the standard baseline |
Changing a single setting in an existing file — edit it directly |
| Parallel PRs keep conflicting on an append-only table/changelog | The conflict is semantic (same line edited) — that needs a real merge |
Onboarding a repo (also reachable via /configure:repo) |
Configuring Claude Code settings — use /configure:repo |
| Build output (changelogs, lockfiles, generated trees) clutters PR diffs | — |
Context
- Existing attributes: !
find . -maxdepth 1 -name .gitattributes -type f - Shell scripts present: !
find . -name '*.sh' -not -path '*/.git/*' -path '*/scripts/*' - Changelogs: !
find . -name 'CHANGELOG.md' -not -path '*/.git/*' - Generated trees: !
find . -type d -name generated -not -path '*/.git/*' - Rendered diagrams: !
find . -path '*/docs/diagrams/*' -name '*.svg' - Lockfiles: !
find . -maxdepth 3 \( -name 'uv.lock' -o -name 'bun.lock' -o -name 'package-lock.json' -o -name 'pnpm-lock.yaml' \)
Parameters
| Parameter | Description |
|---|---|
--check-only |
Report the proposed additions without writing any file |
--fix |
Apply the safe (zero-risk) additions without prompting |
Default (no flag): propose the additions, write them, and git add the file (staged, not committed).
Execution
Execute this .gitattributes configuration workflow:
Step 1: Read existing state
If a .gitattributes exists (from Context), Read it and record which paths are
already covered. Otherwise plan to create one with a header comment.
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 First seen · 126 lines · 45 tokens per session scan A f8218d071e8f
configure-gitattributes is a skill published in the GitHub repository laurigates/claude-plugins (60 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 1,576 once invoked, about $0.0002 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-03.
Other skills, from other repositories
changelog-summarizing
Use this skill when the user asks to summarize, recap, or post about repository changes in the Shopware AI Coding Tools marketplace since a given date — phrases like "write a changelog post for Discord", "recap this week's commits for Slack", "summarize what shipped since 2026-04-01", "draft a release announcement".…
commit-message-writing
Use this skill when the user explicitly asks to generate, write, draft, or create a commit message, squash commit, commit title, or merge commit message for the Shopware core repository (shopware/shopware). Supports two modes — full commit messages (title + body) for branch commits, and squash merge titles…
morning-brief
Operator's read-only morning view of the current GitHub repo in one pass: open counts per queue label, merge-ready PRs, parked decisions with their RECOMMENDED lines, loop-lane telemetry freshness, and per CI lane the week's failures by class, limit stops, restarts and turn headroom, and model usage per activity and…
realign-file-names
Apply a file-name rename plan one file at a time, one human acceptance each: git mv, rewrite only the reference shapes each citing file's tier allows, rebuild generated records, and sweep for stragglers. Refuses a blanket yes, a range, a glob, and 'all'. Use when: 'apply the rename plan', 'apply FN-...', 'do the docs…
feature-branch-pr-writing
Use this skill when the user asks to write, draft, create, or improve a PR description for a Shopware core repository PR — AND that PR targets a non-trunk feature branch (not trunk itself). Trigger phrases like "write a PR description", "draft the PR", "what should I put in the PR body". The skill detects the target…
issue-analyzing
Use this skill when the user asks to analyze a specific GitHub issue, understand what area of code an issue affects, assess an issue's scope, or research the code context around an issue — example triggers like "analyze issue.