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.
git clone --depth 1 https://github.com/hzeng-otterai/ai-course-exampleWrote 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/commands/hzeng-otterai/ai-course-example/add-feature-workflow)<a href="https://agentmods.dev/commands/hzeng-otterai/ai-course-example/add-feature-workflow"><img src="https://agentmods.dev/badge/commands/hzeng-otterai/ai-course-example/add-feature-workflow/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/commands/hzeng-otterai/ai-course-example/add-feature-workflow"><img src="https://agentmods.dev/badge/commands/hzeng-otterai/ai-course-example/add-feature-workflow.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.00000 | $0.00786 |
| Opus 5 | $0.00000 | $0.00393 |
| Sonnet 5 | $0.00000 | $0.00157 |
| Haiku 4.5 | $0.00000 | $0.00079 |
Grade A, and why
add-feature-workflow 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 9d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CRITICAL: Follow this workflow for every feature implementation or refinement. Do not skip or reorder steps.
You are implementing or refining a feature for the GreatNotes app (Django REST Framework backend + React 19 frontend). Work through the steps below in order, pausing for explicit approval before editing any code.
Step 1 — Confirm context
Before anything else, verify:
- Current git branch (
git branch --show-current) - Working directory (confirm you are in
notebook_app_by_cc/) - Any uncommitted changes (
git status)
Report these findings to the user. If there are uncommitted changes, ask whether to proceed or stash first.
Step 2 — Understand the requirement
Restate the feature request in your own words in 2–3 sentences. Call out any ambiguities or edge cases you see. Ask the user to confirm or correct your understanding before continuing.
Step 3 — Identify affected areas
Map out every file likely to change, grouped by layer:
| Layer | Files |
|---|---|
| DB schema | backend/notebooks/models.py, new migration |
| Backend | serializers, views, permissions, urls |
| Frontend | components, API modules, context, routes |
| Tests | backend/notebooks/tests.py, frontend test files |
Flag any cross-cutting concerns (auth, permissions, React Query cache keys, TipTap content shape).
Step 4 — Produce a plan and get approval
Write a numbered implementation plan. For each step include:
- What file changes and why
- Any new model fields or migrations needed
- API contract changes (new endpoints, modified request/response shape)
- Frontend data-flow changes (new query keys, mutation invalidations)
Do not edit any files until the user explicitly approves this plan.
Step 5 — Implement in layer order
Work strictly in this sequence to avoid import errors and broken intermediate states:
- DB schema first — update
models.py, then runpython manage.py makemigrationsandpython manage.py migrate - Backend — serializers → permissions → views → urls (in that dependency order)
- Frontend — API modules (
api/) → context/hooks → components → routes
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.
- 9d ago First seen · 102 lines · 0 tokens per session scan A 5c392f9a5eb2
add-feature-workflow is a command published in the GitHub repository hzeng-otterai/ai-course-example (11 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 786 tokens. 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-30.
Other commands, from other repositories
bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
usage-add
PitWay: Accumulate measured planning or qa token usage onto a milestone.
dashboard
Generar dashboard HTML local con métricas de eficiencia del proyecto SDD.
hub-tdd
TDD workflow for MCP Hub implementation. Types → Tests (red) → Implementation (green) with git gates.
eval
Evaluate and improve one healthcare agent's system prompt. Run up to 5 iterations of: prepare fixed questions -> answer -> judge -> improve -> re-score -> commit if better.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.