Magister 1

Fetch schedule, grades, and infractions from https://magister.net 🇳🇱 portal

Security Scan

The skill's requirements and behavior match its stated purpose (a Magister CLI) and the requested credentials are proportional to that purpose.

Purpose & Capability

Name/description request node and MAGISTER_HOST/MAGISTER_USER/MAGISTER_PASSWORD which are exactly what's needed to authenticate and call the Magister APIs; no unrelated services or binaries are requested.

Instruction Scope

SKILL.md only instructs running the included CLI commands. The implementation does create a local token cache file (.token_cache.json) and performs OIDC flows against accounts.magister.net; the README does not mention the cache file, so users should be aware tokens will be stored locally.

Install Mechanism

No install spec — instruction-only (plus included JS files). It relies on node being present; nothing is downloaded from external URLs or installed automatically.

Credentials

Only MAGISTER_HOST, MAGISTER_USER, MAGISTER_PASSWORD are required, which are appropriate for logging into Magister. Test files reference optional .env file paths for running integration tests, but the main CLI does not parse those files itself.

Persistence & Privilege

The skill writes a .token_cache.json in the same directory to store access tokens (keyed by host:user). It does not request system-wide privileges, nor is always:true set, but users should note local persistence of tokens.

Assessment

This skill is coherent with its description: it needs your Magister host, username, and password to perform the OIDC login and call Magister APIs. If you install/use it, be aware it will create a .token_cache.json file beside the script containing access tokens (remove or restrict permissions if you have concerns). Only run the included tests if you trust the repository and you understand they may read .parent.env/.child.env files for credentials. Verify MAGISTER_HOST is correct and that you trust the accounts.magister.net domain before supplying credentials.

Commands

node magister.mjs students                       # list students (works for parent and child credentials)
node magister.mjs schedule <id> <from> <to>      # schedule, YYYY-MM-DD dates
node magister.mjs grades <aanmelding_id> [top]   # grades (default top=50)
node magister.mjs infractions <id> <from> <to>   # absences

Flow

Run students first to get each student's id and aanmelding_id. Use id for schedule and infractions, aanmelding_id for grades.