django-smoke-alarm
Skill6 starsChanged 4 months agoMITView on GitHub
Run and triage Django/DRF security smoke checks before shipping or after scanner findings.
- Reads credentials
In this repository27 other files it gives its agents.
- agent-skills-agentsAGENTS.md
- agent-skills-claudeCLAUDE.md
- agent-log-forensicsSkill
- changelog-writerSkill
- chezmoi-driftSkill
- contacts-unifySkill
- decision-logSkill
- dependency-pinningSkill
- empathy-auditSkill
- first-contactSkill
- handle-prSkill
- launch-sequenceSkill
- parallel-isolated-app-testingSkill
- post-mortemSkill
- pre-mortemSkill
- profile-meSkill
- ralph-loopSkill
- release-operatorSkill
- remote-host-verifierSkill
- research-personSkill
- scope-hammerSkill
- second-opinionsSkill
- status-copy-trust-auditSkill
- support-stormSkill
- trust-auditSkill
- visual-qa-loopSkill
- wide-open-brainstormSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 5 are distinctive, and 9 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Use this when a Django or DRF project needs a fast security/reliability sweep, especially after a tool such as djangoSecurityHunter, …
- Very specific: line 23
Before launch, deploy, CI hardening, or exposing new auth/API/upload/HTML surfaces.
- Very specific: line 24
When adding or reviewing settings, DRF auth, OAuth/API keys, XML/Markdown/HTML rendering, import jobs, or admin previews.
- Distinctive: line 28
Always classify scanner output before fixing:
- Distinctive: line 34
Do not create a giant undifferentiated fix list.
- Distinctive: line 42
Never judge raw scanner counts from a working repo if it contains worktrees or generated/vendor folders.
- Very specific: line 53
If using djangoSecurityHunter, prefer a clean temp copy and scan-only env values:
- Very specific: line 101
Do not blindly wrap long-running workflows in transaction.atomic().
- Distinctive: line 125
If the same issue could recur, add a project-local guardrail:
- Distinctive: line 131
Import/idempotency tests with duplicate input and repeated runs.
- Very specific: line 153
Use trust-audit for user-facing permission, privacy, billing, and unsafe-feeling AI/data flows found during the scan.
- Very specific: line 154
Use empathy-audit after fixes to catch developer/support burden from noisy scanner-driven changes.
- Very specific: line 155
Use release-operator if this creates a CI/release gate.
- Very specific: line 156
Use decision-log if choosing to accept a scanner false positive or defer a real risk.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Django Smoke Alarm
Use this when a Django or DRF project needs a fast security/reliability sweep, especially after a tool such as djangoSecurityHunter, Bandit, Semgrep, or a custom grep pass reports many findings.
Third-order stance: the goal is not “make the scanner green.” The goal is to find the few boring Django foot-guns that become production incidents, while teaching the project a repeatable preflight. Smoke alarms should be loud, cheap, and easy to silence only with evidence.
When to Use
- The project is Django/DRF and you need obvious security or reliability issues.
- A scanner reports many findings and you need a grounded triage.
- Before launch, deploy, CI hardening, or exposing new auth/API/upload/HTML surfaces.
- When adding or reviewing settings, DRF auth, OAuth/API keys, XML/Markdown/HTML rendering, import jobs, or admin previews.
Core Rule
Always classify scanner output before fixing:
- REAL — plausible exploit/data-loss/abuse path or broken production posture.
- HYGIENE — low-risk but worth making safer/clearer, often to reduce future mistakes.
- FALSE POSITIVE — scanner pattern is misleading; document why with code evidence.
Do not create a giant undifferentiated fix list. The dragon is usually three lizards in a trench coat.
<process>Phase 1: Prepare a Clean Scan
Never judge raw scanner counts from a working repo if it contains worktrees or generated/vendor folders.
Exclude at minimum:
.git .hg .svn .venv venv node_modules dist build .tox .eggs
.mypy_cache .pytest_cache htmlcov coverage
.worktrees .claude/worktrees
.env .env.*If using djangoSecurityHunter, prefer a clean temp copy and scan-only env values:
# run from the project root; script path is relative to this skill's directory
python3 <path-to-this-skill>/scripts/django_smoke_alarm.py \
--project . \
--settings myproject.settings \
--project-python .venv/bin/python \
--scanner-source /tmp/djangoSecurityHunter/src \
--env SECRET_KEY=dummy-scan-only-not-production-40-plus-chars \
--env DEBUG=False \
--env ALLOWED_HOSTS=localhost,127.0.0.1 \
--env DATABASE_URL=sqlite:////tmp/django-smoke.sqlite3The SECRET_KEY above is a placeholder for scan-only use; never put a real secret in scan env values. If the scanner cannot import settings, keep static findings but explicitly say which settings-backed checks were skipped.
Phase 2: Read the Rule Buckets, Not Just Counts
Group findings by risk surface:
- Production settings —
DEBUG,SECRET_KEY,ALLOWED_HOSTS, HTTPS redirect, HSTS, secure cookies, CSRF trusted origins, CORS. - DRF/API abuse — default authentication, permissions, throttles, pagination, auth-like routes, upload limits.
- Unsafe HTML —
mark_safe,|safe, XML/Markdown renderers, admin previews, template tags, rich text blocks. - Persistence races —
exists/get + create, multi-save workflows,save()in loops, arithmetic updates withoutF(), missing uniqueness/idempotency. - Model integrity — natural-key slugs, nullable unique-ish fields, risky cascade deletes, missing constraints.
- Secrets/logging — token-looking defaults, exception logs near OAuth/API keys, local
.env*accidentally tracked. - Dependencies and external scanners — pip-audit, Bandit, Semgrep, only after the clean project scan is understood.
Phase 3: Sample Before Fixing
For each noisy rule, inspect representative code before deciding.
Unsafe HTML triage
Classify as REAL if untrusted or external content is inserted into safe HTML without escaping:
- XML or Markdown source from outside the team
- user profile/team/org/bill/client fields
- uploaded file metadata
- admin preview fields backed by user content
Classify as HYGIENE if the string is constant or all interpolated variables are escaped, but the code would be safer with format_html() / format_html_join().
Classify as FALSE POSITIVE only when the full data path is safe and future edits are unlikely to reintroduce unsafe interpolation.
Transaction/race triage
Do not blindly wrap long-running workflows in transaction.atomic(). Multi-save progress markers around external API calls, Celery jobs, or imports may be intentional.
Prefer:
- DB uniqueness constraints for idempotency.
get_or_create()/update_or_create()where appropriate.select_for_update()for concurrent mutation of existing rows.F()expressions for arithmetic updates.- Small atomic sections around related DB writes, not around network calls or long LLM/image work.
Phase 4: Produce a Triage Table
Report a compact table:
| Finding | Classification | Evidence | Recommended move |
| Missing HSTS | REAL | settings.py has no SECURE_HSTS_SECONDS under DEBUG=False | Add production security block or env-controlled settings |
Admin mark_safe preview | HYGIENE | URL is escaped, constant HTML otherwise | Convert to format_html |
| AI pipeline multiple saves | FALSE POSITIVE/HYGIENE | Saves status before/after long external calls | Do not wrap whole function; maybe add comment/tests |
Then list only the top 3-7 REAL fixes. Put hygiene work behind those. Cite file:line for every row, and stop after the table; apply fixes only if the user asks.
Phase 5: Turn Findings into Project Policy
If the same issue could recur, add a project-local guardrail:
settings.pyproduction security block and test.- DRF throttle defaults and per-route throttles for auth/OAuth/API-key endpoints.
- HTML renderer helper that escapes text by default and marks only known tags safe.
- Code-review note: “no
mark_safewith interpolation; useformat_html.” - Import/idempotency tests with duplicate input and repeated runs.
- CI smoke-alarm job that runs on a clean copy and stores JSON/SARIF artifacts.
</process><tooling>scripts/django_smoke_alarm.py creates a clean temp copy, runs djangoSecurityHunter if available, writes JSON, and prints a grouped summary. It is intentionally a wrapper, not the source of truth: the agent still must read code and classify findings.
Useful flags:
--project— Django repo root.--settings— Django settings module.--project-python— project venv Python, recommended for settings import.--scanner-source— localdjangoSecurityHunter/srccheckout to add toPYTHONPATH.--env KEY=VALUE— scan-only env overrides.--output-dir— report destination.
</tooling><interlocks>- Use
trust-auditfor user-facing permission, privacy, billing, and unsafe-feeling AI/data flows found during the scan. - Use
empathy-auditafter fixes to catch developer/support burden from noisy scanner-driven changes. - Use
release-operatorif this creates a CI/release gate. - Use
decision-logif choosing to accept a scanner false positive or defer a real risk.
</interlocks>Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

