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 rules/jntmtmtm/eisland/test-file-locationgit clone --depth 1 https://github.com/JNTMTMTM/eIslandWrote 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/rules/jntmtmtm/eisland/test-file-location)<a href="https://agentmods.dev/rules/jntmtmtm/eisland/test-file-location"><img src="https://agentmods.dev/badge/rules/jntmtmtm/eisland/test-file-location.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.00144 | $0.00144 |
| Opus 5 | $0.00072 | $0.00072 |
| Sonnet 5 | $0.00029 | $0.00029 |
| Haiku 4.5 | $0.00014 | $0.00014 |
Grade A, and why
test-file-location 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 4d 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 4d ago First seen · 16 lines · 144 tokens per session scan A edae1b280e09
test-file-location is a cursor rule published in the GitHub repository JNTMTMTM/eIsland (308 stars, last pushed today), licensed GPL-3.0. It adds 144 tokens to every session, about $0.0007 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-30.
Other cursor rules, from other repositories
frontend-web
Frontend web development guidelines for React, TanStack Router, and TanStack Query.
cursor-rules
How to add or edit Cursor rules in our project.
ts
Cursor rule "ts" from un-pany/v3-admin-vite, covering ts 开发规范, 类型, 命名, 代码组织 and 错误处理.
sync-shadcn
Autogoal-backed planning, status, review, dashboard, apply, and tracking for upstream shadcn docs syncs into Plate docs. Use when the user asks for sync-shadcn, sync-shadcn status, sync-shadcn review, sync-shadcn dashboard, sync-shadcn apply, a scoped sync-shadcn lane, to sync shadcn docs, audit newer shadcn docs…
clawsweeper
Triage and process the Slate v2 issue ledger with OpenClaw-style sweep discipline: archive-first discovery, duplicate proof, small-fix gates, exact claim rules, maintainer-safe issue output, and gitcrawl API refreshes.
repair-drift
Use when repairing slate-v2 drift against legacy with strict source-first recovery.