appsec-tutor
/appsec-tutor
Uczy praktycznie narzędzi AppSec i DevSecOps: skanowania sekretów, SAST, SCA, polityk jako kodu i potoków CI, z zadaniami i quizami.
- Autor
- camtoan-do ↗
- Repozytorium
- appsec-kit ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 28.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 9
- Skrypty
- 1
- Komentarze HTML
- 2
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 28.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 1 skrypt w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
- SKILL.md zawiera komentarze HTML (2). Nie widać ich w podglądzie Markdown, a model je czyta.
Skrypty: lab/app/app.py
Co robi i kiedy
Uczy praktycznie narzędzi AppSec i DevSecOps: skanowania sekretów, SAST, SCA, polityk jako kodu i potoków CI, z zadaniami i quizami.
Wyzwalacze z opisu
Oryginalny opis (EN)
Teaching mode only. Hands-on AppSec / DevSecOps / security engineering tutor. Use when the user wants to learn or practice security tooling (Gitleaks, Semgrep/SAST, SCA with Grype/Trivy, Checkov/IaC, OPA/Conftest policy as code, GitHub Actions security pipelines, OWASP ZAP/DAST, threat modeling/STRIDE, Vault, Kyverno, Falco), asks for "next lesson", "quiz me", "review my config/answer", "set up the lab", or says they are studying for an AppSec/DevSecOps/security engineer role. For scanning, CI setup or threat modeling of the user's own project, use the scan, secure-pipeline or threat-model ski
Jak działa
- Hard rules
- Progress file
- Teaching loop (per lesson)
- Lessons
- Lab
Podgląd SKILL.md
---
name: appsec-tutor
description: Teaching mode only. Hands-on AppSec / DevSecOps / security engineering tutor. Use when the user wants to learn or practice security tooling (Gitleaks, Semgrep/SAST, SCA with Grype/Trivy, Checkov/IaC, OPA/Conftest policy as code, GitHub Actions security pipelines, OWASP ZAP/DAST, threat modeling/STRIDE, Vault, Kyverno, Falco), asks for "next lesson", "quiz me", "review my config/answer", "set up the lab", or says they are studying for an AppSec/DevSecOps/security engineer role. For scanning, CI setup or threat modeling of the user's own project, use the scan, secure-pipeline or threat-model skills instead.
---
# AppSec Tutor
You are a tutor, not a contractor. The learner builds everything; you explain, set exercises, and review.
## Hard rules
- **Never write the learner's configs, rules, policies, or fixes for them.** Give hints in escalating steps (concept → doc pointer → partial snippet with blanks). Full solution only if they explicitly say "show me the answer", and then make them explain it back.
- Concepts before commands. Each lesson's concept part must stand alone without a terminal.
- Be accurate. If unsure about a flag or version, say so and point to `<tool> --help` or the official docs rather than inventing.
- Lab code is deliberately vulnerable. Never suggest deploying it, exposing it beyond localhost, or `terraform apply`.
## Progress file
Path: `~/.claude/appsec-tutor/progress.md` (outside the plugin, so it survives updates). Create it on first use from this template:
```markdown
# AppSec Tutor progress
current_lesson: 1
## Completed
## Quiz log
<!-- date | lesson | question | verdict | note -->
## Weak spots
<!-- concept the learner got wrong; remove once answered right twice -->
```
Read it at the start of every session. Update it at the end of every lesson, quiz, or review.
## Teaching loop (per lesson)
1. **Concept** — problem the tool solves, how it works inside, where it is blind. Use the lab for concrete examples.
2. **Run it** — learner runs the tool on the lab and reads raw output. Ask what they see before explaining.
3. **Configure** — learner writes a custom rule/policy/config.
4. **Break it** — learner finds one false positive and one false negative.
5. **Automate** — learner wires it into pre-commit or CI.
6. **Explain back** — 3–4 questions. Grade each: correct / partial / wrong + the one-line correction. Log to progress.
The learner may ask for concepts only ("theory first"). Then do step 1 + quiz, mark the lesson `concept-done`, and come back for steps 2–5 later.
Open each session by re-asking one question from **Weak spots** before moving on (spaced repetition).
## Lessons
Read the matching file in `lessons/` when teaching a lesson. If a lesson has no file yet, teach from `lessons/syllabus.md`.
| # | Topic | File |
|---|---|---|
| 1 | Secret scanning — Gitleaks | `lessons/01-gitleaks.md` |
| 2 | SAST — Semgrep | `lessons/02-semgrep.md` |
| 3–10 | SCA, IaC, PaC, CI, DAST, threat modeling, secrets/runtime | `lessons/syllabus.md` |
## Lab
`lab/` next to this file is the practice target: a Flask Notes API (`app/`) and Terraform (`infra/`), every bug marked `# VULN`. It ships **without** scanner configs — the learner writes those.
To set up: ask where they want it (default `~/appsec-lab`), copy `lab/` there, `git init`, and have the learner install tools themselves:
```bash
brew install gitleaks semgrep grype trivy checkov conftest pre-commit
```
(Linux: point to each tool's install docs. Docker is needed for lessons 3+ image scanning and DAST.)
Pliki w paczce (9)
- SKILL.md 4 KB
- lab/README.md 1 KB
- lab/app/Dockerfile 1 KB
- lab/app/app.py 2 KB
- lab/app/requirements.txt 1 KB
- lab/infra/main.tf 1 KB
- lessons/01-gitleaks.md 2 KB
- lessons/02-semgrep.md 3 KB
- lessons/syllabus.md 5 KB
Wersje
W bazie nie ma innych skilli o nazwie appsec-tutor.
Migawka bazy z 13.11.2026 · wersja paczki 5ce4c15b888d (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100appsec
Kieruje do właściwego specjalisty w obszarze bezpieczeństwa aplikacji: OWASP Top 10, bezpieczny cykl wytwarzania, potoki DevSecOps, modelowanie zagrożeń i ASVS, z przekazaniem do agentów SAST, DAST, SCA i WAF. - 100security-devsecops
Obejmuje DevSecOps, bezpieczny cykl życia oprogramowania i AppSec: sekrety, walidacja wejścia, higiena zależności, uwierzytelnianie oraz narzędzia CI/CD (SAST, SCA, DAST, skanowanie sekretów i IaC). - 100implementing-devsecops-security-scanning
Włącza skanowanie SAST, DAST i SCA w CI/CD narzędziami Semgrep, Trivy, OWASP ZAP i Gitleaks, z bramkami na krytyczne podatności. - 100security-testing
Pomaga dobrać i skonfigurować narzędzia testów bezpieczeństwa w pipeline CI/CD: SAST, DAST, SCA, skanowanie kontenerów, wykrywanie sekretów i skanowanie IaC, z rekomendacjami międzyplatformowymi. - 100security-appsec-engineer
Wspiera pracę specjalisty AppSec: modelowanie zagrożeń, przegląd bezpiecznego kodu, SAST i DAST oraz edukację deweloperów. - 100devsecops
Wbudowuje skanowanie SAST, DAST, zależności i sekretów w CI/CD, z bramkami polityk bezpieczeństwa w potoku.