agentleFS
bamlabbamlab/flashlight/.claude/skills/security-findings/SKILL.md

security-findings

Skill1.6k starsChanged 3 days agoMITView on GitHub

Route a security, secret or GDPR finding to the right private place instead of a public issue. Use whenever you have found a vulnerability, leaked secret, personal-data exposure or GDPR gap — from an audit, a review, or while working on something else.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before creating, search for an existing open issue on the same file:line and comment there instead of filing a duplicate.

    line 50
  2. Very specific:

    If you can't reach these private repos (outside contributor), don't file anything public: open a private security advisory at …

    line 52

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Security findings

Security and GDPR findings are never written in the public repo (bamlab/flashlight): not in an issue, a PR, a commit message or a code comment.

Route

finding
 ├─ a live secret is exposed ──────────────► STOP. Tell the maintainer now (it must be rotated). Don't write the value anywhere.
 ├─ a public dependency CVE (already disclosed) ► normal fix PR is fine; reference the advisory ID
 ├─ in the CLI stack (bamlab/flashlight) ───► private issue in bamlab/flashlight-internal
 │                                             (or a private security advisory on bamlab/flashlight
 │                                              when an outside reporter must be credited)
 └─ in the cloud stack (bamlab/flashlight-cloud) ► private issue in bamlab/flashlight-cloud

Private issue format

# CLI stack: bamlab/flashlight-internal · cloud stack: bamlab/flashlight-cloud
gh issue create -R bamlab/flashlight-internal \
  --title "security(<area>): <short description>" \
  --label "needs-triage" \
  --body-file <file>

Critical findings (severity critical) keep needs-triage and are also typed and prioritised, so nobody has to fill these in by hand:

gh issue edit <issue-url> --type Task
# then set the native Priority issue field to Urgent:
gh api graphql -f query='{ organization(login: "bamlab") { issueFields(first: 50) { nodes { ... on IssueFieldSingleSelect { id name options { id name } } } } } }'
gh api graphql -f query='mutation { setIssueFieldValue(input: { issueId: "<issue node id>", issueFields: [{ fieldId: "<Priority field id>", singleSelectOptionId: "<Urgent option id>" }] }) { clientMutationId } }'

Body:

  • Severity — critical / high / medium / low (definitions in /gdpr-audit).
  • Kind — secret · vulnerability · personal data · retention · consent.
  • Where — repo and file:line (for public code, say bamlab/flashlight explicitly).
  • What happens — what data or capability is exposed, to whom.
  • Fix — the smallest change that closes it.
  • Found by — the run, audit or session that found it.

Before creating, search for an existing open issue on the same file:line and comment there instead of filing a duplicate.

If you can't reach these private repos (outside contributor), don't file anything public: open a private security advisory at https://github.com/bamlab/flashlight/security/advisories/new, as SECURITY.md describes.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.