plan-forge: Instructions file for GitHub Copilot

.github/instructions/security.instructions.md

plan-forge security.instructions.md is an instructions file for GitHub Copilot from srnichols/plan-forge. It costs 2,080 tokens per session, scanned B, original, MIT.

Security rules for code that accepts input, runs commands, handles secrets, or changes a user's repository.

In plain words
What is it for?
They help developers validate inputs, run commands safely, protect credentials, and control how tools modify project files.
Why use it?
They reduce risks such as command injection, where crafted input causes an unintended shell command to run, and accidental exposure of secrets.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is srnichols/plan-forge's own configuration. It tells GitHub Copilot how to work on plan-forge 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 plan-forge configures →

Reuse

Borrowing it

Nothing to install: this file belongs to srnichols/plan-forge. 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/srnichols/plan-forge/master/.github/instructions/security.instructions.md
Clone the repo
git clone --depth 1 https://github.com/srnichols/plan-forge

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 plan-forge security.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/srnichols/plan-forge/security/github.svg)](https://agentmods.dev/instructions/srnichols/plan-forge/security)
Your own site
<a href="https://agentmods.dev/instructions/srnichols/plan-forge/security"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/security/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 plan-forge security.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/srnichols/plan-forge/security"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,080 This file is loaded in full into every session.
When invoked 2,080 The same file — it is already loaded in full.
Security scan B 2 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.02080 $0.02080
Opus 5.5 $0.00832 $0.00832
Sonnet 5.5 $0.00416 $0.00416
Haiku 4.5 $0.00208 $0.00208

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

Security

Grade B, and why

plan-forge security.instructions.md scanned grade B with 2 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.

Recursive force deletemediumDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

`userTitle = '"; rm -rf ~ #'` exploits the `exec` form. The `spawn` form passes it as a literal title containing punctuation.

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

import { spawn } from 'node:child_process';
.github/instructions/security.instructions.md · 161 lines

How it starts

The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Security Instructions

Plan Forge runs with the user's full shell privileges and orchestrates writes into the user's repository. Every forge_* tool handler, every CLI command, every spawn, and every file write is a security boundary. This file rules the boundaries.


The 6 Rules

1. Use spawn(cmd, [arg, arg]) — never exec(stringWithInput)

exec parses its argument as a shell command. Any user-supplied substring becomes a shell injection vector. spawn with an args array passes each argument literally to the kernel, no shell involved.

// ✅ correct
import { spawn } from 'node:child_process';
const child = spawn('gh', ['issue', 'create', '--title', userTitle, '--body', userBody]);

// ❌ injection vector
import { exec } from 'node:child_process';
exec(`gh issue create --title "${userTitle}" --body "${userBody}"`);

userTitle = '"; rm -rf ~ #' exploits the exec form. The spawn form passes it as a literal title containing punctuation.

Same rule applies to spawnSync, execFile, and PowerShell Start-Process / Invoke-Expression. Use args arrays. If you need shell features (pipes, redirects), pipe the data in code, not via the shell.

2. No eval, no new Function(string), no dynamic require(userInput)

These accept code from a string and execute it. There is no input value sanitisation that makes this safe.

Common smells caught at review:

  • eval(json) — use JSON.parse(json)
  • new Function('return ' + expr) — use a parser library or a small DSL
  • require(path.join(userDir, file)) — use import() with a validated allowlist of paths

3. Validate input at the forge_* handler boundary

Every MCP tool handler is a system boundary. Validate before doing any work:

function handle_forge_thing({ projectPath, mode }) {
  if (typeof projectPath !== 'string' || !projectPath) {
    return { ok: false, error: 'projectPath required' };
  }
  if (mode !== 'fast' && mode !== 'thorough') {
    return { ok: false, error: 'mode must be "fast" or "thorough"' };
  }
  const resolved = path.resolve(projectPath);
  if (!resolved.startsWith(allowedRoot)) {
    return { ok: false, error: 'projectPath escapes allowed root' };
  }
  // ...real work below this line
}

Read the full file on GitHub · 161 lines

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 · 161 lines · 2,080 tokens per session scan B a8a648b98822

Subscribe to this mod's changes

plan-forge security.instructions.md is an instructions file published in the GitHub repository srnichols/plan-forge (6 stars, last pushed today), licensed MIT. It adds 2,080 tokens to every session, about $0.0083 per session on Opus 5.5. A static security scan graded it B with 2 findings (recursive force delete, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

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

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

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