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 agentmods add skills/khaledsaeed18/dotclaude/gitignorenpx skills add KhaledSaeed18/dotclaude --skill gitignoregit clone --depth 1 https://github.com/KhaledSaeed18/dotclaudeWrote 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/khaledsaeed18/dotclaude/gitignore)<a href="https://agentmods.dev/skills/khaledsaeed18/dotclaude/gitignore"><img src="https://agentmods.dev/badge/skills/khaledsaeed18/dotclaude/gitignore.svg" alt="Measured on agentmods" 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 | $0.00061 | $0.01420 |
| Opus 5 | $0.00030 | $0.00710 |
| Sonnet 5 | $0.00012 | $0.00284 |
| Haiku 4.5 | $0.00006 | $0.00142 |
Grade A, and why
gitignore 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 3d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Produce a .gitignore that fits this repo (driven by the stacks actually present, not a generic blob) and fix the common failure where a pattern is added but the file is already tracked, so Git keeps it anyway.
Hard rules: never break these
- Never ignore source. Ignore dependencies, build output, caches, logs, secrets, and local cruft, never the code or config the project needs to build.
- Adding a pattern does not untrack a tracked file.
.gitignoreonly affects untracked files. Already-committed files needgit rm --cached(Step 5) to stop being tracked. - Preserve existing intent. Don't wipe a hand-tuned
.gitignore; merge, dedupe, and organize. Keep custom and negation (!) rules unless they're clearly wrong. - Treat tracked secrets as an incident. A committed
.env, key, or credential is already in history; adding it to.gitignoreandrm --cachedstops future tracking but does not remove it from past commits. Flag it loudly and point to history-rewrite tooling (git filter-repo, BFG) and secret rotation. - Confirm before
git rm --cached. It changes what's tracked and lands in the next commit.
Step 1: Detect the stacks
Scan the repo for what's actually in use rather than guessing:
- Manifests → ecosystem:
package.json(Node),Cargo.toml(Rust),pyproject.toml/requirements.txt/Pipfile(Python),go.mod(Go),pom.xml/build.gradle(Java/Kotlin),Gemfile(Ruby),composer.json(PHP),*.csproj/*.sln(.NET),pubspec.yaml(Dart/Flutter),mix.exs(Elixir). - Frameworks (they add their own build/cache dirs): Next.js (
.next/), Nuxt (.nuxt/), Astro, SvelteKit, Vite (dist/), Angular, Django (*.sqlite3,staticfiles/), Rails, Terraform (.terraform/), etc. - OS files: macOS (
.DS_Store), Windows (Thumbs.db,Desktop.ini), Linux (*~). - Editors/IDEs:
.vscode/,.idea/,*.swp,.fleet/; these typically belong in a global gitignore, but include locally if the team standardizes there. - Tooling: test coverage (
coverage/,.nyc_output/), env files (.env*), local caches (.cache/,.turbo/,__pycache__/).
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.
- 3d ago First seen · 71 lines · 61 tokens per session scan A 31c01b91da87
gitignore is a skill published in the GitHub repository KhaledSaeed18/dotclaude (5 stars, last pushed 2d ago), licensed MIT. It adds 61 tokens to every session and 1,420 once invoked, about $0.0003 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-31.
Other skills, from other repositories
audit-install-state
Read-only audit of a Claude Code INSTALLATION directory, the machine-scope /.claude tree plus /.claude.json. Inventorying every file, separating what the product's own retention sweep already manages from what nothing manages, resolving what each number in a filename actually means before any process-liveness check…
audit-native-overlap
Map native Claude Code surfaces, built-in CLI commands, bundled skills, plugin-backed built-ins, session-provided skills, against the current repo's plugin skills and agents, so a custom component never silently duplicates what Claude Code itself now ships. Bare invocation is a READ-ONLY report: overlap candidates…
audit-prompting-postures
Audit locally-owned instruction components, including skill bodies, agent definitions, hook instruction text, output styles, CLAUDE.md and rules, for MISSING posture guidance the official prompting guide says their purpose needs: delegation criteria/caps in orchestration components, minimal-scope and anti-test-gaming…
draft-auto-mode-rules
Draft an autoMode classifier block for Claude Code by interviewing you about what should and should not be auto-approved, then printing a paste-ready JSON block to stdout. Entries follow the shape the classifier actually reads well: a label, bulleted COVERED / NOT COVERED, one line of rationale. Every section keeps…
observability
Read and report on locally captured Claude Code telemetry, OTEL DuckDB store, collector, optional Aspire dashboard, hook-event JSONL, ccusage, with cross-session trend reports and store pruning. Use when: 'claude observability', 'OTEL', 'collector', 'token burn rate', 'hook latency', 'cost breakdown', 'how am I…
lookup
Look up current library documentation, API references, and code examples via Context7 (ctx7 CLI or the Context7 MCP server, same backend). Use when: 'look up the docs for X', 'what's the API for X', 'how do I configure X', 'latest docs for X', 'check context7 for X', 'how do I migrate to X v2', or whenever a question…