plan-forge frontend.instructions.md

plan-forge frontend.instructions.md is an instructions file for GitHub Copilot from srnichols/plan-forge. It costs 1,485 tokens per session, scanned A, original, MIT.

A set of TypeScript frontend coding guidelines covering React components, project structure, state management, and related patterns. React is a JavaScript library for building user interfaces.

In plain words
What is it for?
It is for building or reviewing TypeScript frontends, especially React applications, with reusable components, hooks, services, and typed data.
Why use it?
It gives an agent consistent rules for organizing and implementing frontend code. This reduces inconsistent component structure and unclear handling of application state.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

Install

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.

agentmods
npx agentmods add instructions/srnichols/plan-forge/frontend
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 frontend.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/srnichols/plan-forge/frontend.svg)](https://agentmods.dev/instructions/srnichols/plan-forge/frontend)
Your own site
<a href="https://agentmods.dev/instructions/srnichols/plan-forge/frontend"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/frontend.svg" alt="Measured on agentmods" height="20"></a>
Per session 1,485 This file is loaded in full into every session.
When invoked 1,485 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.01485 $0.01485
Opus 5 $0.00743 $0.00743
Sonnet 5 $0.00297 $0.00297
Haiku 4.5 $0.00148 $0.00148

Measured 2d ago against content hash d664975cd5b9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

plan-forge frontend.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 2d 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.

presets/typescript/.github/instructions/frontend.instructions.md · 240 lines

How it starts

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

TypeScript Frontend Patterns

Component Architecture

File Organization

src/
├── components/        # Reusable UI components
│   ├── Button/
│   │   ├── Button.tsx
│   │   ├── Button.test.tsx
│   │   └── Button.module.css
│   └── ...
├── pages/             # Route-level components
├── hooks/             # Custom React hooks
├── services/          # API client, auth, state
├── types/             # Shared TypeScript types
└── utils/             # Pure utility functions

Component Patterns

// ✅ Typed props with interface
interface UserCardProps {
  user: User;
  onEdit: (id: string) => void;
  isLoading?: boolean;
}

export function UserCard({ user, onEdit, isLoading = false }: UserCardProps) {
  if (isLoading) return <Skeleton />;
  
  return (
    <div className="user-card">
      <h3>{user.name}</h3>
      <button onClick={() => onEdit(user.id)}>Edit</button>
    </div>
  );
}

State Management

Server State (TanStack Query)

import { useQuery, useMutation, useQueryClient } from '@tanstack/react-query';

function useUsers() {
  return useQuery({
    queryKey: ['users'],
    queryFn: () => api.getUsers(),
  });
}

function useCreateUser() {
  const queryClient = useQueryClient();
  return useMutation({
    mutationFn: (data: CreateUserInput) => api.createUser(data),
    onSuccess: () => queryClient.invalidateQueries({ queryKey: ['users'] }),
  });
}

Non-Negotiable Rules

Type Safety

// ❌ NEVER: `any` in props or state
const [data, setData] = useState<any>(null);

// ✅ ALWAYS: Explicit types
const [data, setData] = useState<User | null>(null);

Error Boundaries

// ✅ Wrap route-level components
<ErrorBoundary fallback={<ErrorPage />}>
  <UserDashboard />
</ErrorBoundary>

Accessibility

// ✅ Always include aria attributes for interactive elements
<button aria-label="Delete user" onClick={handleDelete}>
  <TrashIcon />
</button>

CSS & Styling

CSS Modules (Recommended)

// ✅ Scoped styles — no class name collisions
import styles from './UserCard.module.css';

export function UserCard({ user }: UserCardProps) {
  return <div className={styles.card}>{user.name}</div>;
}

Read the full file on GitHub · 240 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. 2d ago First seen · 240 lines · 1,485 tokens per session scan A d664975cd5b9

Subscribe to this mod's changes

plan-forge frontend.instructions.md is an instructions file published in the GitHub repository srnichols/plan-forge (5 stars, last pushed 3d ago), licensed MIT. It adds 1,485 tokens to every session, about $0.0074 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-09-03.

Related

Other instructions, from other repositories

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,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

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 · 6,785 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 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,469 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens