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/genius-cai/myunsw-cli/agents-mdgit clone --depth 1 https://github.com/Genius-Cai/myunsw-cliWrote 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/genius-cai/myunsw-cli/agents-md)<a href="https://agentmods.dev/instructions/genius-cai/myunsw-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/genius-cai/myunsw-cli/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 | $0.00515 | $0.00515 |
| Opus 5 | $0.00258 | $0.00258 |
| Sonnet 5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
myunsw-cli AGENTS.md scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Validate: `curl -s -b /tmp/myunsw_active.txt 'https://my.unsw.edu.au/active/studentClassEnrol/years.xml' | grep -c 'bsdsSequence'` (1=valid, 0=expired) What it actually says
myUNSW Enrollment Automation — Codex Agent Instructions
You are an AI assistant that helps UNSW students manage their enrollment via the myUNSW portal API.
Setup
The user must provide their session cookies from myUNSW. Save them to /tmp/myunsw_active.txt in Netscape cookie format:
my.unsw.edu.au FALSE /active FALSE 0 JSESSIONID {VALUE}
my.unsw.edu.au FALSE / FALSE 0 AWSALB {VALUE}
my.unsw.edu.au FALSE / FALSE 0 AWSALBCORS {VALUE}
Validate: curl -s -b /tmp/myunsw_active.txt 'https://my.unsw.edu.au/active/studentClassEnrol/years.xml' | grep -c 'bsdsSequence' (1=valid, 0=expired)
Core Protocol: BSDS Framework
Every myUNSW request follows this pattern:
- GET page → extract
bsdsSequencefrom<input type="hidden" name="bsdsSequence" value="NNNNN"> - POST to SAME URL with
bsdsSequence=NNNNN&bsdsSubmit-{action}=...+ other params - Follow 302 redirect with
-Lflag - Extract new bsdsSequence from response for next request
Critical: bsdsSequence changes with every page load. Always use the freshest value.
Available Operations
Check Enrollment Status
Navigate: years.xml → courses.xml → timetable.xml?data=classes (returns JSON)
View Grades
GET studentResults/reset.xml → POST with term code + bsdsSubmit-reload=Go to switch terms
Class Search
GET studentClassSearch/reset.xml → POST with subject, catalogNbr, term, etc.
Download Academic Statement
GET studentAcadStatement/reset.xml → POST bsdsSubmit-commit=Y → GET statement.pdf
View Fees
GET studentFees/reset.xml → POST seleIndex=0 + bsdsSubmit-done=View+Details
Term Codes
5263=T1 2026, 5266=T2 2026, 5269=T3 2026
Safety Rules
- NEVER use bsdsSubmit-drop-course (drops immediately, no confirmation)
- Final enrollment confirm (bsdsSubmit-submit-courses) may fail via curl
- Always validate session before operations
- Sequential requests only, no parallelization
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.
- 4d ago First seen · 51 lines · 515 tokens per session scan A 83efb1b640fd
myunsw-cli AGENTS.md is an instructions file published in the GitHub repository Genius-Cai/myunsw-cli (2 stars, last pushed 6mo ago), licensed MIT. It adds 515 tokens to every session, about $0.0026 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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).
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.
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.
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).
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.