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.
npx agentmods add instructions/truecourse-ai/truecourse/agents-mdgit clone --depth 1 https://github.com/truecourse-ai/truecourseWhat 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 | $0.00689 | $0.00689 |
| Opus 5 | $0.00345 | $0.00345 |
| Sonnet 5 | $0.00138 | $0.00138 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
truecourse AGENTS.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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TrueCourse — Codex Instructions
Key Files to Keep Updated
- PLAN.md — The source of truth for all phases, implementation status, and test plans. When completing work on any phase or sub-task, update the relevant
STATUS:tags. When adding new features or changing scope, update the plan accordingly. - README.md — Must reflect the current state of the project. When adding new packages, endpoints, commands, environment variables, or changing the project structure, update the README to match.
Project Layout
apps/dashboard/client/— Vite + React Router frontend (React Flow graph, Tailwind CSS, dark mode)apps/dashboard/server/— Express + Socket.io HTTP layer that serves the dashboard. Thin adapter over@truecourse/core.packages/core/— Framework-agnostic analysis engine: pipeline, graph/flow services, LLM providers, persistence, config, logger. Consumed by both the CLI and the dashboard server.packages/shared/— Shared Zod schemas and TypeScript typespackages/analyzer/— Tree-sitter + TypeScript Compiler analysis engine (TS/JS/Python)tools/cli/— CLI commands (analyze, dashboard, list, add, rules). Thin adapter over@truecourse/core— does NOT depend on the dashboard server.tests/— All tests (centralized, not colocated). Organized by package:tests/shared/,tests/analyzer/,tests/server/(covers both dashboard-server routes and core services),tests/cli/.tests/fixtures/sample-project/— Realistic multi-service TS/JS repo used by tests
Development Commands
pnpm dev # Start all services (turbo) — file-based store under <repo>/.truecourse/
pnpm build # Build all packages
pnpm build:dist # Build distributable npm package (static frontend + bundled server → dist/)
pnpm test # Run all tests (vitest)
Rules
- No workarounds. Always find and fix the root cause. Do not use hacks, fallbacks, or temporary patches to bypass issues. If something isn't working, investigate why and fix it properly.
- Dev servers. Do not start, stop, or restart dev servers. The user manages
pnpm devfrom their terminal. If a restart is needed (e.g..envchange), tell the user. - Storage. The store is file-based (no DB). Writes go through
packages/core/src/lib/analysis-store.tsviaatomicWriteJson. Reads are mtime-cached onLATEST.json. Concurrent analyses are prevented by.analyze.lock(O_EXCL).
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.
- 3d ago First seen · 41 lines · 689 tokens per session scan A e126b1df2da0
truecourse AGENTS.md is an instructions file published in the GitHub repository truecourse-ai/truecourse (523 stars, last pushed 5d ago), licensed MIT. It adds 689 tokens to every session, about $0.0034 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.
Other instructions, from other repositories
static-analysis AGENTS.md
Instructions for analysis-tools-dev/static-analysis, covering guidelines for ai agents and assistants and 🤖 instructions for the ai.
fallow CLAUDE.md
Claude Code instructions for fallow-rs/fallow, covering fallow repository adapter for claude, knowledge layers, workflow, trust boundary and generated surfaces.
roam-code AGENTS.md
Instructions for Cranot/roam-code, covering agents.md — roam-code development guide, what this project is, documentation hub, where files go (private vs public) and quality discipline (from internal/dogfood/ + agi-in-md).
PhpCodeArcheology CLAUDE.md
Instructions for PhpCodeArcheology/PhpCodeArcheology, covering claude.md — phpcodearcheology, project overview, language, tech stack and project structure.
megalinter CLAUDE.md
Claude Code instructions for oxsecurity/megalinter, covering claude.md, project overview, development setup, shell commands — use rtk and key commands.
prodlint CLAUDE.md
Instructions for prodlint/prodlint, covering claude.md, commands, architecture, scan flow and rule interface.