Borrowing it
Nothing to install: this file belongs to AI-agents-incubator/n8n-pilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/AI-agents-incubator/n8n-pilot/main/.claude/commands/security.mdgit clone --depth 1 https://github.com/AI-agents-incubator/n8n-pilotWrote 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/ai-agents-incubator/n8n-pilot/security)<a href="https://agentmods.dev/commands/ai-agents-incubator/n8n-pilot/security"><img src="https://agentmods.dev/badge/commands/ai-agents-incubator/n8n-pilot/security.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.00007 | $0.00687 |
| Opus 5 | $0.00003 | $0.00344 |
| Sonnet 5 | $0.00001 | $0.00137 |
| Haiku 4.5 | $0.00001 | $0.00069 |
Grade A, and why
security 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 3d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Проведи детальный аудит безопасности кода согласно SECURITY.md.
ВАЖНО: Сначала прочитай SECURITY.md для полного контекста!
Проверь следующее:
1. Валидация входных данных
- Все пользовательские вводы валидируются на сервере
- Используется типобезопасная валидация (Zod или подобное)
- Проверяется длина строк
- Проверяются типы данных
- Проверяются форматы (email, URL, etc)
2. Аутентификация и авторизация
- Проверка аутентификации в каждом Server Action
- Проверка авторизации (user может делать операцию)
- JWT токены проверяются
- Session management корректен
- Нет hardcoded credentials
3. SQL Injection
- Используются параметризованные запросы
- Нет конкатенации SQL строк
- Используется ORM/Query Builder (Supabase)
- Input sanitization присутствует
4. XSS (Cross-Site Scripting)
- Нет использования
dangerouslySetInnerHTML - Используется React (автоэкранирование)
- Markdown рендерится безопасно (react-markdown)
- Нет
eval()илиFunction()
5. CSRF (Cross-Site Request Forgery)
- Server Actions автоматически защищены Next.js
- API routes используют правильные методы
- Критичные операции требуют подтверждения
6. Утечка данных
- Секреты не в коде (используется .env)
- .env в .gitignore
- Ошибки не раскрывают чувствительную информацию
- Логирование не содержит секретов
- API не возвращает лишние данные
7. Rate Limiting
- Публичные endpoints имеют rate limiting
- Защита от brute force
- Защита от DoS
8. HTTPS и Headers
- Используется HTTPS
- Security headers настроены (next.config.js)
- HSTS включен
- CSP настроен
9. Dependencies
- Нет известных уязвимостей (
npm audit) - Зависимости обновлены
- Используются trusted packages
10. Supabase Security
- Row Level Security (RLS) включен
- Политики правильные
- Пользователи видят только свои данные
- Anon key используется правильно
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.
- 3d ago First seen · 91 lines · 7 tokens per session scan A 4dd65aa299b6
security is a command published in the GitHub repository AI-agents-incubator/n8n-pilot (29 stars, last pushed 5mo ago), licensed MIT. It adds 7 tokens to every session and 687 once invoked, about $0.0000 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-09-04.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.