File a low-severity finding as an ordinary public GitHub issue after explicit analyst confirmation.

MITAuto-check passedSecurity

Install Public Issue

skills CLI
$ npx skills add alpha-omega-security/scrutineer --skill public-issue -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install alpha-omega-security/scrutineer public-issue --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/alpha-omega-security/scrutineer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/public-issue .claude/skills/public-issue && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
public-issue
GitHub stars
239
Token cost
~1.3k tokens
SKILL.md length
549 words
Files
2
Skills in repo
48
Repo updated
First seen
Licence
MIT

At a glance

File a low-severity finding as an ordinary public GitHub issue after explicit analyst confirmation.

  • Defence-in-depth misses
  • SKILL.md covers Workspace, Preconditions, Build the issue and File the issue, plus 3 more sections
  • Calls gh; reaches github.com
  • Other bugs that do not warrant coordinated private disclosure

What it does

Public Issue is an agent skill from alpha-omega-security/scrutineer. File a low-severity finding as an ordinary public GitHub issue after explicit analyst confirmation. Use for hardening gaps, defence-in-depth misses, and other bugs that do not warrant coordinated private disclosure.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `schema.json`). Compatibility notes: Needs the gh CLI authenticated with permission to open issues on the upstream GitHub repository. Needs network access to api.github.com and the scrutineer…

It sits in Security. It works with GitHub. The repository describes itself as: Security through scrutiny. The licence is MIT.

When your agent uses it

  • Defence-in-depth misses
  • Other bugs that do not warrant coordinated private disclosure

Example prompts

  • “/public-issue”

Requirements

  • Compatibility (from SKILL.md): Needs the gh CLI authenticated with permission to open issues on the upstream GitHub repository. Needs network access to api.github.com and the scrutineer API. github.com upstreams only. Finding-scoped.

What it can do on your machine

Read from SKILL.md and the folder at commit f3407bf. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Needs the gh CLI authenticated with permission to open issues on the upstream GitHub repository. Needs network access to api.github.com and the scrutineer API. github.com upstreams only. Finding-scoped.

    From compatibility in the SKILL.md frontmatter.

Context cost

Public Issue loads about 1.3k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 549 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~57
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from alpha-omega-security/scrutineer at commit f3407bf, republished under its MIT licence (© alpha-omega-security). 549 words, ~1,319 tokens.

Download SKILL.mdSave it as .claude/skills/public-issue/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
public-issue
description
File a low-severity finding as an ordinary public GitHub issue after explicit analyst confirmation. Use for hardening gaps, defence-in-depth misses, and other bugs that do not warrant coordinated private disclosure.
compatibility
Needs the gh CLI authenticated with permission to open issues on the upstream GitHub repository. Needs network access to api.github.com and the scrutineer API. github.com upstreams only. Finding-scoped.
license
MIT
metadata.scrutineer.version
1
metadata.scrutineer.output_file
report.json
metadata.scrutineer.output_kind
freeform
metadata.scrutineer.requires_remote
true

public-issue

Open an ordinary public GitHub issue for a confirmed low-severity finding that does not need private vulnerability reporting. This is still a disclosure act: do not file unless the analyst has explicitly chosen this skill for this finding.

Workspace

  • ./src — the upstream clone
  • ./context.json — has repository.url, repository.full_name, and the scrutineer block with api_base, token, repository_id, scan_id, finding_id
  • ./report.json — write what you did
  • ./schema.json — shape of report.json

Use the gh CLI for every GitHub call.

Preconditions

Read ./context.json, then GET {api_base}/repositories/{repository_id} and GET {api_base}/findings/{finding_id} with Authorization: Bearer {token}. Refuse to continue by writing {"error": "..."} to report.json and exit 0 if any of these are true:

  • scrutineer.finding_id is missing — this skill is finding-scoped
  • repository.url host is not github.com
  • gh auth status fails — the runner has no GitHub credentials
  • the finding's status is reported, acknowledged, fixed, published, rejected, or duplicate
  • the finding's status is not ready; the analyst must review and mark it ready before public filing
  • the finding's severity is High or Critical; those should stay on the private disclosure path unless the analyst manually overrides outside this skill
  • the finding's production_viability is NON_VIABLE — refuse with {"error": "latest critic assessment is NON_VIABLE; disclosure, public issue filing, and upstream reporting are blocked"}; reassess it if new build or packaging evidence establishes a supported production path
  • the finding already has a reference tagged public-issue (GET {api_base}/findings/{finding_id}/references)
  • the repository has issues disabled: gh api repos/{owner}/{repo} --jq '.has_issues' is not true

Derive {owner}/{repo} from repository.full_name, falling back to parsing repository.url and stripping a trailing .git.

Build the issue

Draft for maintainers, not for scrutineer operators. The title should be concise and non-alarmist. The body must explain:

  • what is wrong
  • where it is in the code, including location when present
  • why it matters despite being low severity
  • suggested fix or hardening direction, using suggested_fix, mitigation, or rating when available

Use the finding's prose (trace, boundary, validation, rating, disclosure_draft, mitigation) as source material, but do not include exploit-heavy detail that would make the issue unsafe for public posting. If the finding only makes sense with exploit instructions, refuse and tell the analyst to use private disclosure instead.

End the body with:

[scrutineer-finding:{finding_id}]

This marker lets re-runs recognise the issue.

GitHub caps issue titles and bodies. Keep the title under 256 characters and the body under 65535 characters; trim from the bottom and set truncated: true in report.json if needed.

Show full SKILL.md (158 more words)Show less

File the issue

Write ./issue.md with the body, then run:

sh
gh issue create --repo {owner}/{repo} --title "$TITLE" --body-file ./issue.md

Pass the title through an environment variable or stdin-safe shell assignment, not by interpolating raw finding text into a command line. Capture the issue URL from stdout. If gh issue create fails, write {"error": "<stderr or response>"} to report.json and do not write back to scrutineer.

Write back to scrutineer

All with Authorization: Bearer {token}:

  • PATCH {api_base}/findings/{finding_id} with {"fields": {"status": "reported"}, "by": "public-issue"}
  • POST {api_base}/findings/{finding_id}/references with {"url": "<issue_url>", "tags": "public-issue", "summary": "Public issue on {owner}/{repo}"}
  • POST {api_base}/findings/{finding_id}/communications with {"channel": "issue", "direction": "outbound", "actor": "public-issue", "body": "Filed public issue on {owner}/{repo}: <issue_url>"}

Output

Write ./report.json:

json
{
  "upstream": "owner/repo",
  "title": "Issue title",
  "url": "https://github.com/owner/repo/issues/123",
  "truncated": false,
  "error": null
}

On refusal or failure, write:

json
{
  "error": "why nothing was filed"
}

Constraints

  • Do not file unless every precondition passes.
  • Do not open private vulnerability reports, pull requests, discussions, or comments.
  • Do not change repository settings.
  • Do not mark the finding reported unless the issue was successfully created.
  • Do not include secrets, private notes, or exploit walkthroughs in the public body.

© alpha-omega-security, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/public-issue of alpha-omega-security/scrutineer.

  • SKILL.md
  • schema.json

Open the folder on GitHubat commit f3407bf

Compare with similar skills

Public Issue next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Public Issue compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Public Issue this skillalpha-omega-security/scrutineer239—~1.3kAutomated safety check: PassMIT
ReleaseZeecka/AperiSolve852—~1.9kAutomated safety check: PassMIT
Triage Codeqlnetdata/netdata81k—~1.8kAutomated safety check: NotesGPL-3.0
Security AdvisoryMidnightBSD/src114—~2.2kAutomated safety check: PassCustom licence
Security Vulnerability Analysiseclipse-ankaios/ankaios125—~1.5kAutomated safety check: PassApache-2.0
Agentic GitHub Actions Auditortrailofbits/skills7.4k6 repos~5.4kAutomated safety check: NotesCC-BY-SA-4.0

Similar skills

  • Release

    Zeecka/AperiSolve

    Cut a new AperiSolve release — bump the version, commit "chore(release): X.Y.Z", tag it, push, and publish a GitHub Release whose notes are computed from the commits since the last tag.

    852 GitHub stars~1.9k tokensUpdated 2 days ago
    SecurityAuto-check passed
  • Triage Codeql

    netdata/netdata

    Inspect, review or triage GitHub Code Scanning alerts, including CodeQL findings; apply verified dismissals when authorized.

    81k GitHub stars~1.8k tokensUpdated today
    SecurityAuto-check: notes
  • Security Advisory

    MidnightBSD/src

    Handle a security fix end to end for MidnightBSD src - triage a FreeBSD security advisory (FreeBSD-SA-) or CVE against this tree, port the fix to master and both stable branches, add the UPDATING…

    114 GitHub stars~2.2k tokensUpdated 5 days ago
    SecurityAuto-check passed
  • Security Vulnerability Analysis

    eclipse-ankaios/ankaios

    Analyze potential Ankaios security vulnerabilities from pasted reports, local evidence, or advisory URLs.

    125 GitHub stars~1.5k tokensUpdated yesterday
    SecurityAuto-check passed
  • Official

    Statically audits GitHub Actions workflows that run AI coding agents, tracing attacker-controlled input to agent prompts and flagging unsafe sandbox, trigger and allowlist settings.

    7.4k GitHub starsUsed in 6 repos~5.4k tokens
    SecurityAuto-check: notes
  • A skill your agent uses when a researcher, maintainer, or contributor found or suspects a malicious skill on ClawHub and needs a private reporting workflow: opening a GitHub private vulnerability…

    143 GitHub stars~1.1k tokensUpdated 2 days ago
    SecurityAuto-check passed

More from alpha-omega-security/scrutineer

All 48 skills in this repo
  • Triage

    alpha-omega-security/scrutineer

    Default pipeline scrutineer runs when a repository is added.

    239 GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Zizmor

    alpha-omega-security/scrutineer

    Audit GitHub Actions workflows with zizmor and explain reported hits using bundled trust-boundary references.

    239 GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Bandit

    alpha-omega-security/scrutineer

    Run bandit against the Python source in the repository and map its hits into the findings shape.

    239 GitHub stars~615 tokensUpdated today
    Auto-check: notes
  • Compliance

    alpha-omega-security/scrutineer

    Audit the repository against the OpenSSF Baseline with darnit, resolve the controls darnit defers to LLM analysis or could not verify, and record per-control verdicts plus the attained Baseline level.

    239 GitHub stars~1.4k tokensUpdated today
    Auto-check: notes
  • Dependencies

    alpha-omega-security/scrutineer

    Run git-pkgs list and sbom against the repository and emit one envelope with per-section status.

    239 GitHub stars~596 tokensUpdated today
    Auto-check passed
  • History

    alpha-omega-security/scrutineer

    Mine repository history for security fixes that were never published as advisories, producing a cached worklist for threat-model and advisory-deep-dive.

    239 GitHub stars~2.9k tokensUpdated today
    Auto-check: notes

Works with

Categories

Questions about Public Issue

What does Public Issue do?

File a low-severity finding as an ordinary public GitHub issue after explicit analyst confirmation. Public Issue is an agent skill from alpha-omega-security/scrutineer. File a low-severity finding as an ordinary public GitHub issue after explicit analyst confirmation.

When should I use Public Issue?

Public Issue fits situations like: defence-in-depth misses; other bugs that do not warrant coordinated private disclosure.

How do I install Public Issue in Claude Code?

Run `npx skills add alpha-omega-security/scrutineer --skill public-issue -a claude-code`. Or copy the skill folder (skills/public-issue in alpha-omega-security/scrutineer) into .claude/skills/public-issue in your project. Claude Code loads it when a task matches its description.

How do I install Public Issue in Codex?

Run `npx skills add alpha-omega-security/scrutineer --skill public-issue -a codex`. Or copy the skill folder (skills/public-issue in alpha-omega-security/scrutineer) into .agents/skills/public-issue in your project. Codex loads it when a task matches its description.

Can I use Public Issue in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alpha-omega-security/scrutineer --skill public-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/public-issue, .gemini/skills/public-issue, .github/skills/public-issue and .opencode/skills/public-issue in your project.

What does Public Issue need to run?

Going by SKILL.md and its folder, Public Issue needs the command-line tools its instructions call (gh). Compatibility (from SKILL.md): Needs the gh CLI authenticated with permission to open issues on the upstream GitHub repository. Needs network access to api.github.com and the scrutineer API. github.com upstreams only. Finding-scoped..

Does Public Issue access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Public Issue safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Public Issue use?

Public Issue is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Public Issue use?

About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Public Issue?

Skills that share tags, products or a category with Public Issue: Release (Zeecka/AperiSolve, 852 stars), Triage Codeql (netdata/netdata, 81k stars), Security Advisory (MidnightBSD/src, 114 stars) and Security Vulnerability Analysis (eclipse-ankaios/ankaios, 125 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Public Issue?

alpha-omega-security (a GitHub organization) maintains it in alpha-omega-security/scrutineer, which has 239 GitHub stars. The repository holds 48 skills in this directory. The repository was last updated on October 9, 2026.

Source: alpha-omega-security/scrutineer on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.