Open-source guardrail
Deleting a test file or test directory
AgentTrail Guard asks you about this by default: you decide before the call runs. Where an agent cannot ask, the call is refused instead.
- Default action
- Ask
- Severity
- High severity
- Pack
- Test tampering
- Library version
- 0.2.1 · Sep 29, 2026
What it does
What it catches, and what it misses
Written into the rule itself, next to what it matches, so you can judge it before you trust it.
Holds a command that deletes a test: rm, unlink, git rm or PowerShell's Remove-Item naming a file that follows a test runner's naming convention — *.test.*, *.spec.*, *_test.go, *_test.py, test_*.py — or a __tests__/, test/, tests/ or spec/ directory, or a file inside one. Deleting the failing test instead of fixing the code leaves a suite that still passes. Deliberately NOT matched: build, report and dependency output — anything under dist/, build/, out/, coverage/ or node_modules/, and test-results/, playwright-report/ and .pytest_cache — and moving or staging a test (mv, git add). Misses a test deleted with find … -delete, moved out of the tree, emptied or disabled with a file tool, and a test directory with any other name. A quoted MENTION is not a use: a search, a git commit -m message, an echo or a curl --data body that only names this command is left alone. That holds only while every shell metacharacter stays inside the quotes, so git commit -m "x" && … is still caught; and the carrier must be the first word, so sudo grep … is not exempt.
Examples
Tested on every build
The rule must match every command on the left and none on the right, or the library does not build. Catching the real thing is easy; staying quiet on the near-miss is the hard part.
Catches (11)
- rm src/parser.test.ts
- git rm src/__tests__/billing.test.ts
- rm -rf src/__tests__
- rm -rf tests/
- rm test_billing.py
- rm internal/parser/parser_test.go
- git rm -r spec/models
- unlink e2e/login.spec.ts
- rm -f src/a.ts src/a.test.ts
- rm src/test/java/com/example/BillingTest.java
- PowerShellRemove-Item -Recurse -Force tests
Stays quiet on (15)
- git commit -m "docs: explain rm src/parser.test.ts"
- grep -rn "rm src/parser.test.ts" docs/
- echo "never run rm src/parser.test.ts"
- curl --data "we ran rm src/parser.test.ts" https://api.example.com/comments
- npm test
- rm -rf test-results/
- rm coverage/lcov-report/index.html
- rm dist/parser.test.js
- rm -rf node_modules/.vitest
- rm -rf .pytest_cache playwright-report
- git add src/foo.test.ts
- mv src/a.test.ts src/b.test.ts
- rm src/test-utils.ts
- rm -rf testdata/tmp
- rm attest_report.py
In your agent
What "ask" means in each app
The guard runs as a hook in each app, and each app gives a hook different powers. Here is what this rule's default action does in each one.
- Claude Code
- You are asked before the call runs. If your settings.json already allows the tool outright, Claude Code runs it with no prompt.
- Cursor
- A terminal command that reaches the guard gets Cursor's approval card. Any other call that needs approval, such as a file edit or a read, is refused, because Cursor cannot ask there.
- Codex CLI
- Codex cannot ask, so the call is refused, and the reason says a person has to approve it.
Each app hands the guard a different set of calls: in a Cursor sandbox run mode, for one, some terminal commands run without reaching the guard at all. Read the notes for Cursor and for Codex CLI before you rely on a rule there.
Make it yours
Change what it does in one command
Turn it off, change its action, or silence it on one command shape. The narrow one is allow: the rule keeps catching everything else.
Run it locally
Put these guardrails in front of your agent.
AgentTrail Guard is free and open source. It checks every command and file change against the whole library before your agent runs it, on your machine, with no account.
npm i -g @agenttrail/guard