security

Name: security
Rating: 5 (4 reviews)
Author: n-n-code

Security workflow skill for repo-grounded threat modeling, exploit-focused security review, and secure-by-default implementation guidance. Use when the user explicitly asks for security work, or when security properties are the primary concern in a high-risk change. Do not trigger for ordinary code review, routine endpoint work, or general backend implementation just because a repo contains APIs,

4stars

Updated last month

View on GitHub ↗License: MIT

How to add

/plugin marketplace add n-n-code/n-n-code-skills

The exact command may vary by repository. Check the README on GitHub.

For the skill author

Drop this on your repo README

Shows your skill is listed on Skillteca, generates a backlink and trackable traffic.

[![Listada na Skillteca](https://www.skillteca.com.br/api/badge/security-n-n-code/svg)](https://www.skillteca.com.br/skills/security-n-n-code?utm_source=badge&utm_medium=readme&utm_campaign=badge)

#ai #api

Related skills

See all in Automação →

MoneyPrinterTurbo

84.1k

利用AI大模型，一键生成高清短视频 Generate short videos with one click using AI LLM.

Automaçãoby harry0703

weather-svg-creator

55.6k

Creates an SVG weather card showing the current temperature for Dubai. Writes the SVG to orchestration-workflow/weather.svg and updates orchestration-workflow/output.md.

Automação#aiby shanraisshan

telegram-bot-builder

39.2k

Expert in building Telegram bots that solve real problems - from

Automação#github#gitby sickn33

segment-automation

39.2k

Automate Segment tasks via Rube MCP (Composio): track events, identify users, manage groups, page views, aliases, batch operations. Always search tools first for current schemas.

Automação#github#gitby sickn33

Category alert

Get new Automação skills every Monday

One short email with only the new Automação skills. 4 minutes of reading, no spam, unsubscribe with one click.

You confirm your email on the first send. No spam. Unsubscribe with one click.

Security

This skill adds security-specific guidance.

Default Stance

prioritize realistic attacker goals, attacker-controlled input, and concrete impact
ground claims in actual code, entrypoints, data flows, trust boundaries, and deployment shape
research the broader repo before reporting a vulnerability; do not flag pattern matches in isolation
report high-confidence exploit paths first and separate them from lower-confidence follow-up checks
prefer secure defaults that do not

[Description truncada. Veja o README completo no GitHub.]

ShareX LinkedIn

Comments · No comments

No comments yet. Be the first.