faf-cli copilot-instructions.md

Repository instructions for faf-cli, a TypeScript command-line tool that stores persistent AI context in a versioned .faf file. Its show command renders that context for people to read.

In plain words
What is it for?
Use it when working on faf-cli or projects that create, version, inspect, or display .faf persistent AI-context files.
Why use it?
It tells a coding assistant the project's technology, purpose, and expected commands before it changes the repository.

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/wolfe-jam/faf-cli/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/Wolfe-Jam/faf-cli

Made for: GitHub Copilot.

Per session 320 This file is loaded in full into every session.
When invoked 320 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.00320 $0.00320
Opus 5 $0.00160 $0.00160
Sonnet 5 $0.00064 $0.00064
Haiku 4.5 $0.00032 $0.00032

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

Security

Grade A, and why

faf-cli 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 · 24 lines

What it actually says

GitHub Copilot Instructions — faf-cli v6

Authored from project.faf by FAF. Copilot reads these instructions on every request in this repository — keep them short and broadly applicable.

CLI for the .faf format — persistent AI context that versions with your code, and (v6.7, The HTML Edition) renders human-visible on-demand via faf show. IANA-registered media type: application/vnd.faf+yaml.

Tech stack

  • Language: TypeScript

Project context

  • Who: Developers and teams using AI coding assistants
  • What: Persistent AI Context Standard — project DNA for AI. IANA-registered. Anthropic-merged.
  • Why: Eliminates 91% context re-discovery tax — define once, AI remembers forever
  • Where: npm registry, Homebrew, GitHub
  • When: Production since September 2025; v7.0 The GIT Version, June 2026
  • How: bunx faf-cli auto, then project.faf versions with your code — faf show renders it human-visible
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 · 24 lines · 320 tokens per session scan A 156b5885fbd6

Subscribe to this mod's changes

faf-cli copilot-instructions.md is an instructions file published in the GitHub repository Wolfe-Jam/faf-cli (34 stars, last pushed 10d ago), licensed MIT. It adds 320 tokens to every session, about $0.0016 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.