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 skills/reggiechan74/cc-plugins/backward-design-methodologynpx skills add reggiechan74/cc-plugins --skill backward-design-methodologygit clone --depth 1 https://github.com/reggiechan74/cc-pluginsWrote 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/reggiechan74/cc-plugins/backward-design-methodology)<a href="https://agentmods.dev/skills/reggiechan74/cc-plugins/backward-design-methodology"><img src="https://agentmods.dev/badge/skills/reggiechan74/cc-plugins/backward-design-methodology.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.1 | $0.00100 | $0.02727 |
| Opus 5 | $0.00050 | $0.01363 |
| Sonnet 5 | $0.00020 | $0.00545 |
| Haiku 4.5 | $0.00010 | $0.00273 |
Grade A, and why
backward-design-methodology 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 6d 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 — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backward Design Methodology
Overview
Backward design (Understanding by Design/UbD) is a curriculum planning framework that starts with the end in mind. Instead of beginning with content or activities, design courses by first identifying desired learning outcomes, then determining assessment evidence, and finally planning learning experiences. This approach ensures every workshop component serves a clear purpose and students achieve measurable results.
For 1-2 day intensive workshops, backward design prevents common pitfalls: content overload, misaligned assessments, and activities that don't advance learning objectives. The framework creates focused, achievable curricula that maximize learning in compressed timeframes.
The Three Stages of Backward Design
Stage 1: Identify Desired Results
Start by answering: "What should students be able to do by the end of this workshop?"
Define learning outcomes:
- Use measurable, observable action verbs (see blooms-taxonomy skill)
- Focus on 3-5 core outcomes for 1-day workshops, 5-8 for 2-day workshops
- Align outcomes with student needs and market positioning
- Ensure outcomes are achievable within the timeframe
Distinguish between:
- Worth being familiar with: Background knowledge, context, nice-to-know information
- Important to know: Key concepts, fundamental principles, essential vocabulary
- Enduring understanding: Core insights students will retain long-term, transferable skills
For intensive workshops, prioritize enduring understanding. Avoid the coverage trap—don't try to teach everything. Select the most impactful outcomes students can reasonably achieve in 1-2 days.
Example outcomes for 2-day PropTech workshop:
- Analyze PropTech use cases using established frameworks (Porter's Five Forces, value chain analysis)
- Evaluate PropTech solutions for specific real estate challenges with defined criteria
- Create implementation roadmaps for PropTech adoption in traditional real estate contexts
What ships with it
4 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.
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.
- 6d ago First seen · 286 lines · 100 tokens per session scan A 6eeb1da00b3c
backward-design-methodology is a skill published in the GitHub repository reggiechan74/cc-plugins (6 stars, last pushed 3mo ago), licensed MIT. It adds 100 tokens to every session and 2,727 once invoked, about $0.0005 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
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
miniapp
Build a tiny interactive HTML playground only when someone asks to see, play with, or step through a mechanism.
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
deck-course-module
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
best-practices
Searchable knowledge base of 152+ programming best practices across 30+ languages and frameworks. BM25-powered search over curated resources from industry leaders (Google, Airbnb, Uber, Mozilla, Shopify, OWASP).
ark-documentation
Guidance for structuring Ark documentation using the Diataxis framework. Use this skill when creating new docs, deciding where content belongs, reviewing documentation PRs, or restructuring existing documentation.