Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ricneves-ai/flowgrammers-skillsnpx agentmods add skills/ricneves-ai/flowgrammers-skills/red-teamWrote 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/skills/ricneves-ai/flowgrammers-skills/red-team)<a href="https://agentmods.dev/skills/ricneves-ai/flowgrammers-skills/red-team"><img src="https://agentmods.dev/badge/skills/ricneves-ai/flowgrammers-skills/red-team/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ricneves-ai/flowgrammers-skills/red-team"><img src="https://agentmods.dev/badge/skills/ricneves-ai/flowgrammers-skills/red-team.svg" alt="Reviewed on agentmods" width="80" 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.00068 | $0.04441 |
| Opus 5 | $0.00034 | $0.02220 |
| Sonnet 5 | $0.00014 | $0.00888 |
| Haiku 4.5 | $0.00007 | $0.00444 |
Grade A, and why
red-team 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 9d 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 — 338 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Red Team
Skill de planejamento de engajamento de red team e análise de caminho de ataque para simulações de segurança ofensiva autorizadas. Isto NÃO é varredura de vulnerabilidades (veja security-pen-testing) ou resposta a incidentes (veja incidente-response) — trata-se de simulação adversária estruturada para testar detecção, resposta e eficácia dos controles.
Sumário
- Visão Geral
- Ferramenta de Planejamento de Engajamento
- Metodologia de Fases da Kill-Chain
- Pontuação e Priorização de Técnicas
- Análise de Pontos Críticos
- Avaliação de Risco OPSEC
- Identificação de Alvos de Alto Valor
- Metodologia de Caminho de Ataque
- Fluxos de Trabalho
- Anti-Padrões
- Referências Cruzadas
Visão Geral
O que esta Skill Faz
Esta skill fornece a metodologia e as ferramentas para planejamento de engajamento de red team — construção de planos de ataque estruturados a partir da seleção de técnicas MITRE ATT&CK, nível de acesso e alvos de alto valor. Ela pontua técnicas por esforço e risco de detecção, monta fases de kill-chain, identifica pontos críticos e sinaliza riscos OPSEC.
Distinção de Outras Skills de Segurança
| Skill | Foco | Abordagem |
|---|---|---|
| red-team (esta) | Simulação adversária | Ofensiva — planejamento e execução de ataques estruturados |
| security-pen-testing | Descoberta de vulnerabilidades | Ofensiva — exploração sistemática de fraquezas específicas |
| threat-detection | Encontrar atividade de atacante | Proativa — detectar TTPs na telemetria |
| incidente-response | Gestão de incidentes ativos | Reativa — conter e investigar incidentes confirmados |
Requisito de Autorização
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.
- 9d ago First seen · 338 lines · 68 tokens per session scan A 8f173fe22941
red-team is a skill published in the GitHub repository ricneves-ai/flowgrammers-skills (112 stars, last pushed 3mo ago), licensed MIT. It adds 68 tokens to every session and 4,441 once invoked, about $0.0003 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-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…