Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add terrylica/cc-skills/plugin install statusline-toolsWrote 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/terrylica/cc-skills/ignore)<a href="https://agentmods.dev/skills/terrylica/cc-skills/ignore"><img src="https://agentmods.dev/badge/skills/terrylica/cc-skills/ignore/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/terrylica/cc-skills/ignore"><img src="https://agentmods.dev/badge/skills/terrylica/cc-skills/ignore.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.00032 | $0.01068 |
| Opus 5 | $0.00016 | $0.00534 |
| Sonnet 5 | $0.00006 | $0.00214 |
| Haiku 4.5 | $0.00003 | $0.00107 |
Grade B, and why
ignore scanned grade B with 1 finding 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 5d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat ~/.claude/lint-relative-paths-ignore 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.
Navigation: Plugin CLAUDE.md | Root CLAUDE.md
Global Ignore Patterns
Manage global ignore patterns for the lint-relative-paths linter.
Self-Evolving Skill: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.
Purpose
Some repositories intentionally use relative paths in markdown (e.g., ../docs/file.md)
instead of repo-root paths (e.g., /docs/file.md). This command manages a global ignore
file that skips path validation for matching workspaces.
Actions
| Action | Description | Example |
|---|---|---|
add |
Add a pattern to the global ignore file | /statusline-tools:ignore add my-repo |
list |
Show current patterns | /statusline-tools:ignore list |
remove |
Remove a pattern from the ignore file | /statusline-tools:ignore remove my-repo |
Pattern Matching
Patterns use substring matching. A pattern matches if the workspace path contains the pattern.
Example: Pattern alpha-forge matches:
/Users/user/projects/alpha-forge/Users/user/eon/alpha-forge.worktree-feature-x/home/user/code/alpha-forge-v2
Ignore File Location
~/.claude/lint-relative-paths-ignore
Lines starting with # are comments.
Execution
Skip Logic
- If action + pattern provided -> execute directly
- If only
listprovided -> show patterns immediately - If no arguments -> use AskUserQuestion flow
Workflow
- Check Current State: Run
listto show existing patterns - Action Selection: Use AskUserQuestion to select action:
- "Add a new pattern" -> prompt for pattern
- "Remove an existing pattern" -> show current patterns to select
- "Just view current patterns" -> display and exit
- Pattern Input: For add/remove, AskUserQuestion with examples
- Execute: Run the management script
- Verify: Confirm changes applied
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 126 lines · 32 tokens per session scan B 316df97ea0f2
ignore is a skill published in the GitHub repository terrylica/cc-skills (72 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 1,068 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
Other skills, from other repositories
debug-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.
backpropagation
Trace runtime bugs back to spec gaps — identify missing acceptance criteria, update specs, generate regression tests, and detect patterns.
investigate-root-cause
Use when encountering ANY bug, error, test failure, or unexpected behavior. Activate for keywords like "bug", "error", "failing", "broken", "doesn't work", "unexpected", "crash", "exception", "TypeError", "undefined", stack traces, or any error message. Also trigger when tests fail unexpectedly, when behavior differs…
evidence-driven-debugging
Use during active debugging when you have a hypothesis to test or need to instrument a running system. Activate for keywords like "debug", "instrument", "log", "trace", "breakpoint", "what's happening at runtime", "production behavior". Pair to investigate-root-cause for the doing-it phase. Always record what you…
map-codebase
Use when entering an unfamiliar codebase or area, before making non-trivial changes, when onboarding to a new system, or when planning a refactor that touches multiple modules. Activate for keywords like "explore", "map", "find where", "trace", "how does X work", "what calls Y", "scope of change". Produces an…
github-actions-silent-failures
Diagnose GitHub Actions workflows that fail silently — a reusable-workflow run that shows zero jobs and no logs (startupfailure), a gh-aw cross-repo import that mis-resolves when the source repo is literally named .github, and self-hosted-runner traps (a shared-tmp race across containers, docker exec landing as an…