Borrowing it
Nothing to install: this file belongs to QTtrash/tarkov-map. 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/QTtrash/tarkov-map/main/AGENTS.mdgit clone --depth 1 https://github.com/QTtrash/tarkov-mapWrote 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/instructions/qttrash/tarkov-map/agents-md)<a href="https://agentmods.dev/instructions/qttrash/tarkov-map/agents-md"><img src="https://agentmods.dev/badge/instructions/qttrash/tarkov-map/agents-md/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/instructions/qttrash/tarkov-map/agents-md"><img src="https://agentmods.dev/badge/instructions/qttrash/tarkov-map/agents-md.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.00353 | $0.00353 |
| Opus 5.5 | $0.00141 | $0.00141 |
| Sonnet 5.5 | $0.00071 | $0.00071 |
| Haiku 4.5 | $0.00035 | $0.00035 |
Grade A, and why
tarkov-map AGENTS.md 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 2mo 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
Agent guide
Raid Signal is a Windows Tauri application plus a separately deployed Node.js relay and static phone companion. Treat this file as an index; follow the linked documents instead of duplicating their details in prompts or code comments.
Start here
docs/ARCHITECTURE.md— runtime boundaries, data flow, and module ownership.docs/SECURITY.md— trust boundaries and invariants that changes must retain.docs/QUALITY.md— the one-command verification contract and test ownership.CONTRIBUTING.md— environment setup and pull-request expectations.ASSET_LICENSES.md— non-code asset scope, provenance, and restrictions.
Non-negotiable invariants
- Never read game memory, inject input, alter game files, or claim anti-cheat approval.
- Invitation keys stay in URL fragments and must never reach or be logged by the relay.
- The relay forwards ciphertext only and stores no position history.
- Keep existing settings schema v2 and room protocol v1 compatible.
- Do not commit installers, build outputs, secrets, personal deployment paths, or refreshed assets without their hashes and provenance.
- Validate data at every filesystem, storage, native-command, and network boundary before treating it as an application type.
Working loop
- Read the owning module and its nearest tests before editing.
- Keep behavior changes separate from formatting and structural extraction.
- Run the narrowest relevant test while iterating.
- Run
npm run check:allbefore handing work off. - Use a Conventional Commit pull-request title and explain why, compatibility, security/privacy impact, and validation in the body.
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.
- 2mo ago First seen · 36 lines · 353 tokens per session scan A dc87f8a4f951
tarkov-map AGENTS.md is an instructions file published in the GitHub repository QTtrash/tarkov-map (6 stars, last pushed 12d ago), licensed Apache-2.0. It adds 353 tokens to every session, about $0.0014 per session on Opus 5.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.
tarkov-map AGENTS.md compared with instructions from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| tarkov-map AGENTS.mdQTtrash/tarkov-map | Instructions file | 6 | 12d ago | Apache-2.0 | A | 353 | Codex, OpenCode |
| vscode buildNext.instructions.mdmicrosoft/vscode | Instructions file | 195k | yesterday | MIT | A | 9,719 | GitHub Copilot |
| next.js AGENTS.mdvercel/next.js | Instructions file | 143k | yesterday | MIT | A | 7,461 | Codex, OpenCode |
| langchain AGENTS.mdlangchain-ai/langchain | Instructions file | 149k | yesterday | MIT | A | 4,680 | Codex, OpenCode |
| vscode oss-third-party-notices.instructions.mdmicrosoft/vscode | Instructions file | 195k | yesterday | MIT | A | 5,516 | GitHub Copilot |
| vscode copilot-instructions.mdmicrosoft/vscode | Instructions file | 195k | yesterday | MIT | A | 3,093 | GitHub Copilot |
| deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness | Instructions file | 274k | 2d ago | MIT | A | 4,313 | Codex, OpenCode |