11 Recipe directory
One page indexing every recipe: theme section, level, tools used. Level counts are hand-counted until the directory generator lands (the directory + Top-10 views lane), then they regenerate from the recipe headers at build time and this page becomes a generated artifact — never hand-counted again.
11.1 At a glance
| Section | Recipes | Easy | Medium | Hard |
|---|---|---|---|---|
| Getting started | 3 | 3 | 0 | 0 |
| Scanning | 1 | 1 | 0 | 0 |
| Attack–defence pairs | 1 | 0 | 0 | 1 |
| Ops | 1 | 0 | 1 | 0 |
| Administrator | 3 | 1 | 2 | 0 |
11.2 Recipes
| Recipe | Section | Level | Tools |
|---|---|---|---|
| Boot a verified release image | Getting started | easy | kailash images |
| First profile and first run | Getting started | easy | kailash CLI |
| Enable your first category | Getting started | easy | kailash categories |
| Scan a self-hosted model for prompt-injection resistance | Scanning | easy | garak |
| Attack the platform, then verify | Attack–defence pairs | hard | mlflow-bypass + mlflow |
| Serve a local model for scanning | Ops | medium | ollama |
| Refresh wordlists and data packs | Administrator | easy | kailash-data packs |
| Ride a release without breaking pinned tooling | Administrator | medium | flake update |
| Gate lab-mode and exp-classified tools | Administrator | medium | lab-mode gate |
11.3 Top-10 collections (generated views, planned)
Per the organisation ADR, Top-10 collections render as build-time generated index pages over recipe tags — recipes never move between sections. Planned sets: OWASP LLM Top-10 (the garak recipe already carries llm01; mappings per manifest row), OWASP ML Top-10, OWASP API Top-10. No collection page renders until its tagged recipes exist — never an empty view.