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 skills add Canvas-LMS-MCP/canvas-teacher-mcp --skill git-asmt-repogit clone --depth 1 https://github.com/Canvas-LMS-MCP/canvas-teacher-mcpWrote 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/skills/canvas-lms-mcp/canvas-teacher-mcp/git-asmt-repo)<a href="https://agentmods.dev/skills/canvas-lms-mcp/canvas-teacher-mcp/git-asmt-repo"><img src="https://agentmods.dev/badge/skills/canvas-lms-mcp/canvas-teacher-mcp/git-asmt-repo/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.
<a href="https://agentmods.dev/skills/canvas-lms-mcp/canvas-teacher-mcp/git-asmt-repo"><img src="https://agentmods.dev/badge/skills/canvas-lms-mcp/canvas-teacher-mcp/git-asmt-repo.svg" alt="Reviewed on agentmods" width="80" 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.00126 | $0.05802 |
| Opus 5 | $0.00063 | $0.02901 |
| Sonnet 5 | $0.00025 | $0.01160 |
| Haiku 4.5 | $0.00013 | $0.00580 |
Grade A, and why
git-asmt-repo 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 12d 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 — 359 lines — stays where its author put it; the contents beside it link to each section on GitHub.
git-asmt-repo — GLOBAL abstract (L1)
The language-agnostic core of "build + test a GitHub coding assignment for the org-hub." It owns
the procedure and the gates; it never says g++, pytest, or Catch2. Those live in L2 language
skills; the course id/org/prefix/curriculum live in the L3 course wrapper.
L1 (this) git-asmt-repo/SKILL.md ← WHAT: audit · fidelity · prove-100 · ship · gates
L2 git-asmt-repo/languages/ ← HOW in a language: compile/run/assert
python-pytest.md · cpp-stdout.md · cpp-catch2.md
L3 (local) <course>/.claude/skills/…-git… ← WHICH: org, prefix, language, chapter→model map (config)
The seams L1 leaves lower layers = four slots. Three are L2 (language): COMPILE, RUN,
ASSERT(case). One is L3 (course + term): PROVISION — HOW the local dir → repo → Starter is
created, which differs per course and changes per semester (see Part C). L1 calls all four abstractly;
L2 fills compile/run/assert for the language, the L3 wrapper/config fills provision for the course.
The CORE RULE (inherited by every L2): classroom.yml IS the test spec — run its command:
lines verbatim, in its order. Never assume the method or infer it from the files present. Step 0
of any test is always: open the repo's .github/workflows/classroom.yml and read its graders + order.
⛔ STEP 0b — DIFF THE REPO AGAINST ITS L2 TEMPLATE, EVERY BUILD. The harness files have ONE source, per language:
languages/<cpp-catch2|cpp-stdout|python-pytest|java-junit>/template/
…/.github/workflows/classroom.yml ← the true grader config
+ the harness files that model needs (tests, runner, Makefile, .gitignore, README)
An existing course repo is a COPY of some older template and drifts silently. Before building,
shipping, or "fixing" anything, diff the repo's classroom.yml against its template and say out
loud which graders differ. Never edit a repo's yml to correct it — change the TEMPLATE, then
propagate (local dir → solution master → Starter, all three, per Part C). The CORE RULE above
still governs how you RUN an already-released repo; this governs what a NEW one is built from.
(2026-08-02: three repos each carried a retired -fsanitize=address grader; the template
had dropped it long before, and no skill file said where the template lived.)
What ships with it
36 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- languages/cpp-catch2.md 5.0 KB
- languages/cpp-catch2/template/.github/workflows/classroom.yml 2.8 KB
- languages/cpp-catch2/template/.gitignore 86 B
- languages/cpp-catch2/template/catch.hpp 647 KB
- languages/cpp-catch2/template/main.cpp 292 B
- languages/cpp-catch2/template/main.hpp 585 B
- languages/cpp-catch2/template/Makefile 263 B
- languages/cpp-catch2/template/README.md 510 B
- languages/cpp-catch2/template/tests.cpp 1.6 KB
- languages/cpp-stdout.md 3.3 KB
- languages/cpp-stdout/template/.github/workflows/classroom.yml 2.9 KB
- languages/cpp-stdout/template/.gitignore 227 B
- languages/cpp-stdout/template/data/data1.txt 4 B
- languages/cpp-stdout/template/data/data2.txt 6 B
- languages/cpp-stdout/template/data/run.sh 419 B runs code
- languages/cpp-stdout/template/main_test.py 2.1 KB runs code
- languages/cpp-stdout/template/main.cpp 553 B
- languages/cpp-stdout/template/Makefile 303 B
- languages/cpp-stdout/template/pytest.ini 202 B
- languages/cpp-stdout/template/README.md 494 B
- languages/java-junit.md 7.3 KB
- languages/java-junit/template/.github/workflows/classroom.yml 3.7 KB
- languages/java-junit/template/.gitignore 81 B
- languages/java-junit/template/data/input.txt 6 B
- languages/java-junit/template/lib/junit-platform-console-standalone-1.10.2.jar 2618 KB
- languages/java-junit/template/README.md 1.5 KB
- languages/java-junit/template/src/Main.java 199 B
- languages/java-junit/template/test/MainTest.java 3.5 KB
- languages/python-pytest.md 3.3 KB
- languages/python-pytest/template/.github/workflows/classroom.yml 2.8 KB
- languages/python-pytest/template/.gitignore 355 B
- languages/python-pytest/template/data/data.txt 10 B
- languages/python-pytest/template/main_test.py 1.7 KB runs code
- languages/python-pytest/template/main.py 672 B runs code
- languages/python-pytest/template/pytest.ini 189 B
- languages/python-pytest/template/README.md 406 B
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.
- 12d ago First seen · 359 lines · 126 tokens per session scan A 02a483639e5d
git-asmt-repo is a skill published in the GitHub repository Canvas-LMS-MCP/canvas-teacher-mcp (1 stars, last pushed 27d ago), licensed MIT. It adds 126 tokens to every session and 5,802 once invoked, about $0.0006 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 skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.