systematic copilot-instructions.md

A set of coding rules for the Systematic project, including its programming tools, project conventions, and required checks.

In plain words
What is it for?
Use it when changing Systematic code to check project structure, write compatible imports, and run the required build, type checks, linting, and tests.
Why use it?
It gives a coding agent one place to find the repository’s rules and prevents it from using the wrong runtime, test tool, package manager, or import style.

Instructions file for GitHub Copilot

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/marcusrbrown/systematic/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/marcusrbrown/systematic

Made for: GitHub Copilot.

Per session 1,027 This file is loaded in full into every session.
When invoked 1,027 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 $0.01027 $0.01027
Opus 5 $0.00513 $0.00513
Sonnet 5 $0.00205 $0.00205
Haiku 4.5 $0.00103 $0.00103

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

Security

Grade A, and why

systematic copilot-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.

.github/copilot-instructions.md · 142 lines

How it starts

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

Copilot Instructions for Systematic

Read AGENTS.md at the repository root before writing any code. It is the canonical source for project structure, conventions, and command reference.

Stack

  • Runtime: Bun (not Node.js, not Deno)
  • Language: TypeScript 5.7+ with strict: true
  • Modules: ESM only ("type": "module" in package.json)
  • Linter: Biome — not ESLint, not Prettier
  • Tests: bun:test with describe/it — not Jest, not Vitest
  • Package manager: Bun — not npm, not pnpm, not yarn

Verification Commands

Run these before marking work complete:

bun run build        # Build to dist/
bun run typecheck    # TypeScript strict mode
bun run lint         # Biome linter
bun test             # Unit and integration tests

All four must pass. Do not skip any.

Do / Don't

Imports

// ✅ Do: node: protocol for builtins
import { readFile } from 'node:fs/promises'
import { join } from 'node:path'

// ✅ Do: .js extension on relative imports (ESM requirement)
import { parseFrontmatter } from './frontmatter.js'

// ✅ Do: import type for type-only imports
import type { SkillConfig } from './types.js'

// ❌ Don't: bare builtin imports
import { readFile } from 'fs/promises'

// ❌ Don't: missing .js extension
import { parseFrontmatter } from './frontmatter'

Type Safety

// ✅ Do: unknown + type guards
function processInput(value: unknown): string {
  if (typeof value !== 'string') {
    throw new TypeError(`Expected string, got ${typeof value}`)
  }
  return value
}

// ✅ Do: explicit return types on exports
export function findSkills(dir: string): Promise<SkillDefinition[]> { ... }

// ❌ Don't: any, @ts-ignore, @ts-expect-error, non-null assertions (!)
function processInput(value: any) { ... }
// @ts-ignore
someCall()!

Architecture

// ✅ Do: functions — this codebase has zero classes
export function createHandler(config: Config): Handler { ... }

// ❌ Don't: classes
class Handler { ... }

Read the full file on GitHub · 142 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 · 142 lines · 1,027 tokens per session scan A dbfe83eeddf5

Subscribe to this mod's changes

systematic copilot-instructions.md is an instructions file published in the GitHub repository marcusrbrown/systematic (24 stars, last pushed 3d ago), licensed MIT. It adds 1,027 tokens to every session, about $0.0051 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-08-30.