What is PixelPilot threat-modeling.instructions.md?

A security review method based on STRIDE, a framework for finding threats such as impersonation, data leaks, and unauthorized access.

It helps assess authentication, user data, payments, uploads, APIs, and admin features, then plan mitigations and security tests.

It exposes security risks before code is written by mapping system boundaries, actors, data flows, and possible attacks.

How dev-lou/PixelPilot configures GitHub Copilot

Reuse

Borrowing it

Nothing to install: this file belongs to dev-lou/PixelPilot. 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/dev-lou/PixelPilot/main/vscode/.github/instructions/threat-modeling.instructions.md

Clone the repo

git clone --depth 1 https://github.com/dev-lou/PixelPilot

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/dev-lou/pixelpilot/threat-modeling/github.svg)](https://agentmods.dev/instructions/dev-lou/pixelpilot/threat-modeling)

Your own site

<a href="https://agentmods.dev/instructions/dev-lou/pixelpilot/threat-modeling"><img src="https://agentmods.dev/badge/instructions/dev-lou/pixelpilot/threat-modeling/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/dev-lou/pixelpilot/threat-modeling"><img src="https://agentmods.dev/badge/instructions/dev-lou/pixelpilot/threat-modeling.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 2,760 This file is loaded in full into every session.

When invoked 2,760 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.

Model	Per session	Once invoked
Fable 5.1	$0.02760	$0.02760
Opus 5.5	$0.01104	$0.01104
Sonnet 5.5	$0.00552	$0.00552
Haiku 4.5	$0.00276	$0.00276

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

Security

Grade A, and why

PixelPilot threat-modeling.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 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.

vscode/.github/instructions/threat-modeling.instructions.md · 356 lines

How it starts

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

Threat Modelling 2026

STRIDE threat model → trust boundary diagram → threat table → mitigations → security test cases. Run before writing security-sensitive code.

THE STRIDE MODEL

Letter	Threat	Violates	Example
S	Spoofing	Authentication	Attacker impersonates admin user
T	Tampering	Integrity	Attacker modifies request payload
R	Repudiation	Non-repudiation	User denies making a purchase
I	Information disclosure	Confidentiality	API leaks other users' data
D	Denial of service	Availability	Flood endpoint to make it unreachable
E	Elevation of privilege	Authorization	Regular user accesses admin endpoint

STEP 1 — DECOMPOSE THE SYSTEM

Before applying STRIDE, map the system using Data Flow Diagrams (text format).

## System Decomposition

### Actors (external entities)
- **Anonymous user** — unauthenticated visitor
- **Authenticated user** — logged-in member
- **Admin** — internal staff with elevated access
- **Third-party service** — Stripe, OAuth provider, email service

### Processes
- **Auth service** — login, registration, session management
- **API gateway** — routes, rate limiting, auth middleware
- **Business logic** — core feature processing
- **Background workers** — async jobs (emails, reports)

### Data stores
- **Primary DB** — user records, transactions
- **Cache** — session tokens, temporary data
- **File storage** — user uploads (S3 / R2)
- **Audit log** — immutable event log

### Trust boundaries (draw these explicitly)
─────────────────────────────────────────
  [ Internet / untrusted zone ]
  ↓ HTTPS ↓
  [ Load balancer / WAF ]          ← Trust boundary 1
  ↓
  [ API gateway + rate limiter ]   ← Trust boundary 2
  ↓
  [ Application server ]
  ↓                    ↓
  [ Primary DB ]   [ External APIs ]  ← Trust boundary 3
─────────────────────────────────────────

STEP 2 — APPLY STRIDE TO EACH COMPONENT

Read the full file on GitHub · 356 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.

2mo ago First seen · 356 lines · 2,760 tokens per session scan A ec5cc08744bf

Subscribe to this mod's changes

PixelPilot threat-modeling.instructions.md is an instructions file published in the GitHub repository dev-lou/PixelPilot (2 stars, last pushed 7mo ago), licensed MIT. It adds 2,760 tokens to every session, about $0.0110 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.

Backend and APIs Data and AI Finance and fintech Frontend ai-prompts copilot cursor-rules design-system developer-tools

PixelPilot threat-modeling.instructions.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
PixelPilot threat-modeling.instructions.mddev-lou/PixelPilot	Instructions file	2	7mo ago	MIT	A	2,760	GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	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

PixelPilot: Instructions file for GitHub Copilot