student-ops AGENTS.md

A set of instructions for coding agents working in the student-ops repository. It defines onboarding checks, request routing, personal-data rules, and how application-tracker changes must be verified and recorded.

In plain words
What is it for?
It is for operating safely in the student-ops codebase. It covers loading the repository's guidance, checking deadlines, storing preferences, and adding or updating application records without duplicates.
Why use it?
Agents may act incorrectly if they skip required project context or update tracked data in the wrong way. These rules set the required checks and write process.

Instructions file for CodexOpenCode

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/apollo887/student-ops/agents-md
Clone the repo
git clone --depth 1 https://github.com/Apollo887/student-ops

Made for: Codex, OpenCode.

Per session 551 This file is loaded in full into every session.
When invoked 551 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.00551 $0.00551
Opus 5 $0.00275 $0.00275
Sonnet 5 $0.00110 $0.00110
Haiku 4.5 $0.00055 $0.00055

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

Security

Grade A, and why

student-ops 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 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.

AGENTS.md · 49 lines

How it starts

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

AGENTS.md

Guidance for AI coding agents (Claude Code, OpenCode, Codex) operating in the student-ops repo.

Primary directive

Read CLAUDE.md first. It is the canonical system brief. Everything here is supplementary.

Before responding to any user message

  1. Silent onboarding check — does config/profile.yml exist? Does modes/_profile.md exist? If either is missing, enter onboarding before doing anything else.
  2. Load context — read CLAUDE.md, modes/_shared.md, and modes/_profile.md for scoring defaults and user customizations.
  3. Detect mode — match the user's request to a mode (see mode routing table in CLAUDE.md). If ambiguous, ask.
  4. Check deadlines — if any deadline is <3 days away, lead the response with it before whatever the user asked.

Data layer rules (CRITICAL)

  • Writes that reflect the user's personal preferences → config/profile.yml or modes/_profile.md
  • Writes that are generic system logic → NEVER. If the user wants the system changed, open an issue / PR.
  • The tracker (data/applications.md) is append-or-update — never duplicate.
  • New tracker rows go via batch/tracker-additions/ + merge-tracker.mjs. Never hand-edit.

Verification rules

  • School data (admit rates, deadlines, middle-50 stats) → verify on the school's official page via Playwright or WebFetch. Never trust WebSearch snippets alone.
  • Financial aid figures → use the exact numbers the student provided, don't estimate.
  • Claims in essays → source must be in profile.yml, a freewrite the student shared, or a prior draft. No fabrications.

Essay rules

  • Multi-pass only. Brainstorm → outline → draft → voice pass → cut. Never one-shot a final.
  • Preserve the student's voice. If you wrote it and it doesn't sound like them, rewrite it.
  • Flag clichés aggressively (see _shared.md red flags).
  • Save every version to essays/{school-slug}-{prompt}-v{n}.md.

Honest counsel

Student-ops is the friend who tells the student the truth. Specifically:

Read the full file on GitHub · 49 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 · 49 lines · 551 tokens per session scan A dea80bfd6ab0

Subscribe to this mod's changes

student-ops AGENTS.md is an instructions file published in the GitHub repository Apollo887/student-ops (5 stars, last pushed 25d ago), licensed MIT. It adds 551 tokens to every session, about $0.0028 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-31.

Related

Other instructions, from other repositories

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

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

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

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,345 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

next.js 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