Borrowing it
Nothing to install: this file belongs to swarm-ai-research/swarm. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/swarm-ai-research/swarm/main/.claude/commands/check_ignore.mdgit clone --depth 1 https://github.com/swarm-ai-research/swarmWrote 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/commands/swarm-ai-research/swarm/check_ignore)<a href="https://agentmods.dev/commands/swarm-ai-research/swarm/check_ignore"><img src="https://agentmods.dev/badge/commands/swarm-ai-research/swarm/check_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/commands/swarm-ai-research/swarm/check_ignore"><img src="https://agentmods.dev/badge/commands/swarm-ai-research/swarm/check_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.00000 | $0.00408 |
| Opus 5 | $0.00000 | $0.00204 |
| Sonnet 5 | $0.00000 | $0.00082 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
check_ignore 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 10d 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.
What it actually says
/check-ignore
Verify that .gitignore won't hide files in a target directory before you create them. Prevents the "wrote 7 files but git can't see them" footgun.
Usage
/check-ignore <path>
Examples:
/check-ignore swarm/bridges/new_bridge//check-ignore swarm/research/new_module/
Behavior
-
Run
git check-ignore -v <path>/__init__.py(use a synthetic filename if the dir doesn't exist yet). -
If ignored, report:
- Which
.gitignorerule is responsible (file, line number, pattern) - Whether the pattern is missing a leading
/anchor (most common cause) - Suggest the fix (e.g.
bridges/→/bridges/) - Ask the user whether to apply the fix
- Which
-
If not ignored, report "Path is visible to git" and proceed.
-
If the fix is applied, verify by re-running
git check-ignoreto confirm the path is now visible.
Why this exists
.gitignore patterns without a leading / match anywhere in the tree. A rule like bridges/ intended for a root-level directory will also match swarm/bridges/live_swe/. Files already tracked before the rule was added remain tracked, but new files in the same parent are silently invisible. This wastes time debugging "why doesn't git status show my files."
Known patterns in this repo
The following .gitignore entries are anchored to root and should stay that way:
/bridges/— root-level relocated directory (notswarm/bridges/)submissions/— root-level submissions dirswarm-api/— root-level API dir
If you add a new gitignore rule for a directory name that also exists under swarm/, anchor it with a leading /.
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.
- 10d ago First seen · 39 lines · 0 tokens per session scan A a9dc59decbd1
check_ignore is a command published in the GitHub repository swarm-ai-research/swarm (42 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 408 tokens. 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-30.
Other commands, from other repositories
eval-merge
Use the Read tool to load .skill-compass/{skill-name}/manifest.json. Verify.
speckit.git.feature
Create a feature branch with sequential or timestamp numbering.
speckit.git.commit
Auto-commit changes after a Spec Kit command completes.
speckit.git.initialize
Initialize a Git repository with an initial commit.
speckit.git.remote
Detect Git remote URL for GitHub integration.
speckit.git.validate
Validate current branch follows feature branch naming conventions.