Borrowing it
Nothing to install: this file belongs to haroontrailblazer/EduOrchestrate. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/haroontrailblazer/EduOrchestrate/main/AGENTS.mdgit clone --depth 1 https://github.com/haroontrailblazer/EduOrchestrateWrote 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.
[](https://agentmods.dev/instructions/haroontrailblazer/eduorchestrate/agents-md)<a href="https://agentmods.dev/instructions/haroontrailblazer/eduorchestrate/agents-md"><img src="https://agentmods.dev/badge/instructions/haroontrailblazer/eduorchestrate/agents-md.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00764 | $0.00764 |
| Opus 5 | $0.00382 | $0.00382 |
| Sonnet 5 | $0.00153 | $0.00153 |
| Haiku 4.5 | $0.00076 | $0.00076 |
Grade A, and why
EduOrchestrate 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 7d 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 — 24 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EduOrchestrate Agent Instructions
Use /eduorchestrate as the learner command. When invoked, load the EduOrchestrate workflow and its prebuilt terminal-card program; never recreate, type out, or hand-design the card UI in the agent prompt. Ask for missing learner profile details, ask what the learner is currently studying, ask the first skill they want to focus on, generate or update an adaptive plan with a fixed 30-day minimum, research current and trending references, send or preview daily emails, log progress, load the bundled default card or CLI-produced card artifact, summarize the week, recommend the next skill after the plan window, and keep recommendations practical, sourced, and focused. Mail resume policy: apply this to every supported agent, not only Codex. When an agent runs in a resumable browser or workspace instance, treat each resume as a daily-mail checkpoint: load the harness or status, resolve the current plan day, and run npx eduorchestrate send-today for the due day after SMTP setup. If SMTP secrets are missing or real sending has not been approved, run npx eduorchestrate send-today --dry-run and ask before sending. GitHub Actions remains the scheduled no-browser path. If native slash commands are unavailable, treat "eduorchestrate" or "use EduOrchestrate" as equivalent to /eduorchestrate.
Command
Expose or honor /eduorchestrate for this repo. If the host agent cannot register slash commands, respond to /eduorchestrate, eduorchestrate, or use EduOrchestrate as the same workflow.
Workflow
- Load
eduorchestrate.config.jsonwhen present. - Ask for missing name, email, target role, current learning topic, first skill focus, current stage, desired plan days, daily email time, and timezone.
- Generate or update
data/30-day-plan.json; never generate fewer than 30 days. - Use
npx eduorchestrate research --day <n>for sourced docs, trend scans, YouTube search, and GitHub sample-code search links. - Send or preview daily email with
npx eduorchestrate send-today --dry-runornpx eduorchestrate send-today; browser/workspace agents must check and send the due daily mail on resume after SMTP setup, while GitHub Actions remains the scheduled no-browser path. - Log evidence with
npx eduorchestrate log-progress --day <n> --completed "..." --evidence "...". - Do not create or type card UI in the agent. Use the prebuilt default card at
skills/eduorchestrate/assets/default-terminal-card.svgor the initialized copy atdata/default-terminal-card.svg. - Load the compact execution harness with
npx eduorchestrate harnessbefore doing research, mail, progress, or review work. - Use
npx eduorchestrate coursesfor role-specific official/MNC course catalogs, free-course discovery links, and newsletters; do not default to Coursera or Udemy. - When learner-specific state is needed, call the prebuilt CLI program with
npx eduorchestrate progress-cardornpx eduorchestrate terminal-card; then loaddata/progression-card.mdordata/terminal-card.svg. - Summarize with
npx eduorchestrate statusandnpx eduorchestrate weekly-summary --week <n>. - Recommend the next skill after the plan with
npx eduorchestrate recommend-next. - Keep the learner focused on one daily build artifact.
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.
- 7d ago First seen · 24 lines · 764 tokens per session scan A b148111e737a
EduOrchestrate AGENTS.md is an instructions file published in the GitHub repository haroontrailblazer/EduOrchestrate (10 stars, last pushed 1mo ago), licensed MIT. It adds 764 tokens to every session, about $0.0038 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.
Other instructions, from other repositories
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.
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).
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.
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.
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).
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.