agent-rules: Instructions file for GitHub Copilot

.github/instructions/file-system.instructions.md

agent-rules file-system.instructions.md is an instructions file for GitHub Copilot from lirantal/agent-rules. It costs 433 tokens per session, scanned A, original, Apache-2.0.

Security rules for Node.js code that reads, writes, or deletes files and works with file paths. They explain how to build paths safely and prevent path traversal, where input escapes the intended directory.

In plain words
What is it for?
Use them when implementing file uploads, downloads, file serving, directory access, or other Node.js file-system operations.
Why use it?
They reduce the risk of users or external data accessing or changing files outside the allowed location. They also promote consistent handling of encoded and normalized paths.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is lirantal/agent-rules's own configuration. It tells GitHub Copilot how to work on agent-rules itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agent-rules configures →

Reuse

Borrowing it

Nothing to install: this file belongs to lirantal/agent-rules. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/lirantal/agent-rules/main/.github/instructions/file-system.instructions.md
Clone the repo
git clone --depth 1 https://github.com/lirantal/agent-rules

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for agent-rules file-system.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/lirantal/agent-rules/file-system/github.svg)](https://agentmods.dev/instructions/lirantal/agent-rules/file-system)
Your own site
<a href="https://agentmods.dev/instructions/lirantal/agent-rules/file-system"><img src="https://agentmods.dev/badge/instructions/lirantal/agent-rules/file-system/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.

agentmods 80×15 button for agent-rules file-system.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/lirantal/agent-rules/file-system"><img src="https://agentmods.dev/badge/instructions/lirantal/agent-rules/file-system.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 433 This file is loaded in full into every session.
When invoked 433 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00433 $0.00433
Opus 5.5 $0.00173 $0.00173
Sonnet 5.5 $0.00087 $0.00087
Haiku 4.5 $0.00043 $0.00043

Measured 1mo ago against content hash 6521bdbfd6a6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

agent-rules file-system.instructions.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 1mo 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.

.github/instructions/file-system.instructions.md · 25 lines

What it actually says

Paths, Files and File System operations security guidelines

Your Mission

As an agent, you are an expert in secure coding practices for file system operations in Node.js. Your mission is to assist developers in creating secure and reliable code in tasks that involve handling file paths and file system operations. You must prioritize security, prevent vulnerabilities such as path traversal, and provide actionable, detailed guidance.

These rules apply any time you are working on code that involves the following type of operations and Node.js core APIs:

  • fs module operations (e.g., reading, writing, deleting files)
  • path module operations (e.g., joining, normalizing paths)

Securely Constructing File Paths

  • You always construct paths using the following 5 steps:
    1. Base Directory: Define a base directory that is the root directory where you want to operate on files.
    2. Decode The Path: Paths may be provided via a URL and so you should always decode the path using decodeURIComponent() to ensure that any encoded characters like %2e%2e%2f are properly converted to their original form ../.
    3. Normalize The Path: Use path.normalize() to clean up the path and remove any redundant segments like . or ... This helps to prevent path traversal vulnerabilities.
    4. Path Construction: Use path.join() or path.resolve()
    5. Path Validation: Ensure that the resulting path does not escape the base directory by checking that it starts with the base directory.
  • When constructing file paths, never concatenate user input directly into the path. Instead, use the path.join() or path.resolve() methods from the Node.js path module to safely construct file paths.
  • When using path.join() or path.resolve(), you must protect against path traversal attacks by ensuring that the resulting path does not escape the intended directory. You can do this by checking that the resulting path starts with the intended base directory.
Changes

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.

  1. 1mo ago First seen · 25 lines · 433 tokens per session scan A 6521bdbfd6a6

Subscribe to this mod's changes

agent-rules file-system.instructions.md is an instructions file published in the GitHub repository lirantal/agent-rules (65 stars, last pushed yesterday), licensed Apache-2.0. It adds 433 tokens to every session, about $0.0017 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-30.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,581 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens