canvas-week-plan

canvas-week-plan is a skill for Claude Code, Codex from JohannsenLum/canvas-api-mcp. It costs 80 tokens per session (826 once invoked), scanned A, original, MIT.

A read-only planning tool for Canvas, a learning-management system used by schools and universities. It finds upcoming coursework, matches it to courses, checks submission status, and orders the work by due date.

In plain words
What is it for?
Use it to ask what is due soon, plan the coming days, or review upcoming assignments with urgency indicators.
Why use it?
It turns scattered assignment and course information into a clear plan, while checking whether work has actually been submitted.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to ask what is due soon, plan the coming days, or review upcoming assignments with urgency indicators.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/johannsenlum/canvas-api-mcp/canvas-week-plan
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.

Any agent
npx skills add JohannsenLum/canvas-api-mcp --skill canvas-week-plan
Clone the repo
git clone --depth 1 https://github.com/JohannsenLum/canvas-api-mcp

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for canvas-week-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/johannsenlum/canvas-api-mcp/canvas-week-plan/github.svg)](https://agentmods.dev/skills/johannsenlum/canvas-api-mcp/canvas-week-plan)
Your own site
<a href="https://agentmods.dev/skills/johannsenlum/canvas-api-mcp/canvas-week-plan"><img src="https://agentmods.dev/badge/skills/johannsenlum/canvas-api-mcp/canvas-week-plan/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for canvas-week-plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/johannsenlum/canvas-api-mcp/canvas-week-plan"><img src="https://agentmods.dev/badge/skills/johannsenlum/canvas-api-mcp/canvas-week-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 826 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00080 $0.00826
Opus 5 $0.00040 $0.00413
Sonnet 5 $0.00016 $0.00165
Haiku 4.5 $0.00008 $0.00083

Measured 11d ago against content hash ffbb99feb323, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

canvas-week-plan 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 11d 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.

skills/canvas-week-plan/SKILL.md · 70 lines

How it starts

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

Canvas Week Plan

Read-only planning skill. Never modify, submit, or post anything: only report what the canvas-api-mcp tools return.

Prerequisites

The canvas-api-mcp MCP server must be installed and connected in the current client. If tool calls to whats_due, my_courses, or my_submission are not available, tell the user to install it first: https://mcp.johannsenlum.com/canvas-lms/install

Procedure

  1. Get upcoming work. Call the MCP tool whats_due to retrieve assignments/items due in the near term. Do not guess or estimate due dates: use only what the tool returns.

  2. Resolve course names. Call my_courses and join each item from step 1 to its course name/code using the course id. Do not invent a course name if it can't be matched: show the raw course id instead and note it's unresolved.

  3. Disambiguate anything unclear. For any item where submission/completion state is ambiguous or missing from step 1's output, call my_submission for that specific assignment to get its authoritative submitted/graded state. Do not assume "not shown" means "not submitted". Check before reporting.

  4. Build the table. Present the results as a single table ordered by due date (soonest first), with these columns:

    • Course (resolved name, or course id + "(unresolved)")
    • Assignment
    • Due date/time
    • Days remaining (compute from the due date and current time only, do not invent a "today" if it isn't available from context)
    • Submitted state (Submitted / Not submitted / Graded / Unknown, from tool output only)
  5. Flag risk items, called out clearly below the table (not buried in it):

    • Anything due within 48 hours that is NOT submitted: flag explicitly, e.g. "DUE SOON, UNSUBMITTED".
    • Any two or more items that share the same due date/day ("same-day collision"): list them together so the student sees the pile-up.
  6. Check whether whats_due actually answered. If it returns {"error": true, ...} with no items key, every source failed to load: that is not an empty schedule. Say Canvas could not be reached and quote the warnings; never turn a failed read into "nothing is due".

Read the full file on GitHub · 70 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. 11d ago First seen · 70 lines · 80 tokens per session scan A ffbb99feb323

Subscribe to this mod's changes

canvas-week-plan is a skill published in the GitHub repository JohannsenLum/canvas-api-mcp (2 stars, last pushed 27d ago), licensed MIT. It adds 80 tokens to every session and 826 once invoked, about $0.0004 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 skills, from other repositories

canvas-cli

Manage Canvas LMS (https://www.instructure.com/canvas) from the terminal with the canvas CLI — courses, assignments, submissions and grading, modules, pages, quizzes, discussions, announcements, users, enrollments, sections, files, and analytics. Use this whenever the user wants to list or create assignments, grade…

jjuanrivvera/canvas-cli · 113 tokens

canvas-admin-roster

Admin skill for walking the Canvas account hierarchy: list accounts and sub-accounts, see courses and users under each, look up which canned reports are available, and enroll or remove users from a specific course — one action at a time. Trigger phrases include "admin roster", "list accounts", "sub accounts", "account…

bruchris/canvas-lms-mcp · 0 tokens

canvas-accessibility-sweep

Educator and learning-designer skill for a pre-launch accessibility and broken-link sweep of a Canvas course. Walks the structural accessibility audit and the link audit over a course's pages, assignments, syllabus, announcements, and (optionally) quizzes, then produces a prioritised remediation list you can work…

bruchris/canvas-lms-mcp · 131 tokens

canvas-office-hours

Educator skill for running office hours through Canvas Scheduler appointment groups. Create and publish sign-up slots for a course, list existing groups and their time slots, and see which students (or student groups) have reserved — one confirmed action at a time. Trigger phrases include "office hours", "appointment…

bruchris/canvas-lms-mcp · 103 tokens

canvas-peer-review-tracker

Educator skill for tracking peer-review assignments in Canvas. Lists who has been asked to review whom, who has submitted versus who is still pending, and lets you assign new reviewers or send reminder messages — one student at a time. Trigger phrases include "peer reviews", "who hasn't done their peer review", "peer…

bruchris/canvas-lms-mcp · 92 tokens

canvas-course-pulse

Educator skill for tracking week-over-week course health trends in Canvas. Surfaces assignment performance trends, login activity, engagement gaps, and struggling students across a longer time horizon than a daily check. Trigger phrases include "course pulse", "course health", "course trends", "week-over-week…

bruchris/canvas-lms-mcp · 90 tokens