agentleFS
Sign inStart free
timothywarner-orgtimothywarner-org/ab900/AGENTS.md

ab900

AGENTS.md29 starsChanged 4 months agoMITView on GitHub

This public repository is the course home for Tim Warner's Pearson class Copilot and Agent Administration Fundamentals (October 27, 2026) and the earlier July 2026 O'Reilly AB-900 course. Start with README.md for the learning route and TUTORIALS.md for the step-by-step exercises. CLAUDE.md holds the full authoring rules for the July course and the study-buddy assets under .github/. - README.md is the Pearson course home in the series layout shared with context-engineering-with-mcp: banner, badges, byline, learning route, what is in the…

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,439 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository5 other files it gives its agents.

The file

We split this AGENTS.md into the rules it gives an agent

8 rules. About 0 are common, 2 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Never edit or re-export these PDFs.

    line 28
  2. Very specific:

    Keep the Pearson story consistent: Contoso, Ltd., pilot user Debra, content owner Kim Akers, and the harmless marker SERVICE-ORCHID-42.

    line 40
  3. Very specific:

    Never turn a NOT RUN row in the test matrix into a result from an expected answer.

    line 44
  4. Very specific:

    Keep instructor operations, schedules, publisher files, correspondence, and credentials out of tracked files.

    line 45
  5. Distinctive:

    Never force-add it. Public checks must work without it.

    line 47
  6. Very specific:

    Don't modify, re-export, or re-hash files under .local/ or the private paths unless explicitly requested.

    line 52
  7. Very specific:

    Run python scripts/Test-CourseHome.py after documentation changes.

    line 57
  8. Distinctive:

    Follow the repository writing rules: plain ASCII, no curly quotes, and no em dashes or en dashes.

    line 60

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

Learner-facing AB-900 course home

This public repository is the course home for Tim Warner's Pearson class Copilot and Agent Administration Fundamentals (October 27, 2026) and the earlier July 2026 O'Reilly AB-900 course. Start with README.md for the learning route and TUTORIALS.md for the step-by-step exercises. CLAUDE.md holds the full authoring rules for the July course and the study-buddy assets under .github/.

Project map

  • README.md is the Pearson course home in the series layout shared with context-engineering-with-mcp: banner, badges, byline, learning route, what is in the repository, lab prerequisites, portals, author bio, and license. The July edition lives in archive/july-2026/, and the exam material in docs/certify.md and docs/study-buddy.md.
  • NOTICE.md holds trademarks, the fictional-data statement, and source attribution.
  • images/banner.png and images/social-preview.png are generated by scripts/make_banner.py from images/brand.json. Change the JSON and rerun the script. Don't hand-edit the PNGs.
  • evidence/ holds the instructor's dated, observed test runs. Never copy them into the starter matrix, which stays NOT RUN for learners.
  • TUTORIALS.md repeats every Pearson demo as numbered steps: prepare a lab, trace access and adoption, create a DLP policy in simulation, read a data access governance report, build and test the starter agent, and approve and operate it.
  • handouts/ holds the four PDF handouts exactly as Pearson distributes them in the session Resources widget (October 19, 2026 bytes, checked by hash), plus a README that maps each one to a tutorial and lists the updates since they were written. Never edit or re-export these PDFs. Record corrections in handouts/README.md.
  • starter-files/ holds the synthetic Contoso, Ltd. service guide, agent instructions, test matrix (T01 to T08, all NOT RUN), and synthetic sharing report.
  • archive/july-2026/ holds the four-hour July edition: notes, demo scripts, labs, segment folders, and shared resources. references/ serves the study buddy. Both belong to the July O'Reilly course.
  • .github/ holds the study-buddy prompts, skills, and instructions.
  • scripts/Test-CourseHome.py checks the course-home documents and the public/private boundary.

Teaching and repository boundaries

  • Keep the Pearson story consistent: Contoso, Ltd., pilot user Debra, content owner Kim Akers, and the harmless marker SERVICE-ORCHID-42. Keep business data fictional.
  • Ground every product claim in a current Microsoft Learn page and link it. Portal paths change, so date the check.
  • Never turn a NOT RUN row in the test matrix into a result from an expected answer.
  • Keep instructor operations, schedules, publisher files, correspondence, and credentials out of tracked files. Store local material under ignored .local/. Never force-add it. Public checks must work without it.
  • Pearson production files live under deliveries/2026-10-pearson/ and .pearson-build/. They are ignored here and tracked in a separate private repository through a second Git directory, .git-pearson. Never add .git-pearson/ or those paths to this public repository.
  • Don't modify, re-export, or re-hash files under .local/ or the private paths unless explicitly requested.

Changes and verification

  • Run python scripts/Test-CourseHome.py after documentation changes. It checks local links and anchors in the course-home documents, the starter files, the writing rules, and the public/private boundary.
  • Follow the repository writing rules: plain ASCII, no curly quotes, and no em dashes or en dashes. Course-home documents use Tim's teaching voice, with contractions and no AI filler phrases, and the checker fails on uncontracted negations there. Exam-item content (archive/july-2026/, .github/ prompts and skills, references/) keeps the no-contraction item-writing rule.
  • Distinguish failures caused by existing worktree changes from failures caused by the current edit. Don't revert or overwrite unrelated changes.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free