Flare

Name: Flare
Author: BiswajitBiswa

ASecurity

File a bug or risk as a flare with a lifecycle

2 stars
0 votes
0 copies
0 views
Added October 3, 2026

ai-agentspython

Security analysis

A100/100

Scanned October 3, 2026

npx -y skills add BiswajitBiswa/cosmos --skill flare --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Flare?

Add the live security badge to your README. It updates with every re-scan.

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/biswajitbiswa-flare/badge)](https://www.skillsdirectory.com/skills/biswajitbiswa-flare)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: flare
description: "File a bug or risk as a flare with a lifecycle"
---
<!-- written by cosmos (`cosmos connect` rewrites it; delete this line to keep your own version) -->
File a flare for: (the text the person typed after the command)
Find the code it is about first and cite it as `path:line`. Then call `cosmos_flare` with `title` (one line, what is wrong), `severity` (critical|high|medium|low), `locations` (`path:line · path:line`), `what`, `impact` and `fix`.
Without the tools: `python3 .cosmos/cosmosw flares add "<severity>: <title> @ <path:line>" --what "…" --impact "…" --fix "…"`.
Several bugs at once (a list a person pasted, one per line, or a .csv / .xlsx / .txt path): one `cosmos_flare` per bug, or `python3 .cosmos/cosmosw flares add --from <file>` (`-` reads stdin).
Do not choose a prefix: cosmos names the flare after the project's lifecycle stage (`python3 .cosmos/cosmosw flares stage` shows it). Reply with the flare id.