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.
File a low-severity finding as an ordinary public GitHub issue after explicit analyst confirmation.
$ npx skills add alpha-omega-security/scrutineer --skill public-issue -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install alpha-omega-security/scrutineer public-issue --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "public-issue" agent skill from https://github.com/alpha-omega-security/scrutineer/tree/main/skills/public-issue into .claude/skills/public-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "public-issue", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/alpha-omega-security/scrutineer/tree/main/skills/public-issueType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add alpha-omega-security/scrutineer --skill public-issue -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install alpha-omega-security/scrutineer public-issue --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alpha-omega-security/scrutineer.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/public-issue .agents/skills/public-issue && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "public-issue" agent skill from https://github.com/alpha-omega-security/scrutineer/tree/main/skills/public-issue into .agents/skills/public-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "public-issue", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alpha-omega-security/scrutineer --skill public-issue -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install alpha-omega-security/scrutineer public-issue --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alpha-omega-security/scrutineer.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/public-issue .cursor/skills/public-issue && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "public-issue" agent skill from https://github.com/alpha-omega-security/scrutineer/tree/main/skills/public-issue into .cursor/skills/public-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "public-issue", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/alpha-omega-security/scrutineer.git --path skills/public-issue--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add alpha-omega-security/scrutineer --skill public-issue -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install alpha-omega-security/scrutineer public-issue --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alpha-omega-security/scrutineer.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/public-issue .gemini/skills/public-issue && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "public-issue" agent skill from https://github.com/alpha-omega-security/scrutineer/tree/main/skills/public-issue into .gemini/skills/public-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "public-issue", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install alpha-omega-security/scrutineer public-issueInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add alpha-omega-security/scrutineer --skill public-issue -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/alpha-omega-security/scrutineer.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/public-issue .github/skills/public-issue && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "public-issue" agent skill from https://github.com/alpha-omega-security/scrutineer/tree/main/skills/public-issue into .github/skills/public-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "public-issue", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alpha-omega-security/scrutineer --skill public-issue -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install alpha-omega-security/scrutineer public-issue --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alpha-omega-security/scrutineer.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/public-issue .opencode/skills/public-issue && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "public-issue" agent skill from https://github.com/alpha-omega-security/scrutineer/tree/main/skills/public-issue into .opencode/skills/public-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "public-issue", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
public-issueFile 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. 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.
Read from SKILL.md and the folder at commit f3407bf. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
ghFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
github.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in 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.
From compatibility in the SKILL.md frontmatter.
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.
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.
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.
The full file from alpha-omega-security/scrutineer at commit f3407bf, republished under its MIT licence (© alpha-omega-security). 549 words, ~1,319 tokens.
.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.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.
./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.jsonUse the gh CLI for every GitHub call.
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-scopedrepository.url host is not github.comgh auth status fails — the runner has no GitHub credentialsstatus is reported, acknowledged, fixed, published, rejected, or duplicatestatus is not ready; the analyst must review and mark it ready before public filingseverity is High or Critical; those should stay on the private disclosure path unless the analyst manually overrides outside this skillproduction_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 pathpublic-issue (GET {api_base}/findings/{finding_id}/references)gh api repos/{owner}/{repo} --jq '.has_issues' is not trueDerive {owner}/{repo} from repository.full_name, falling back to parsing repository.url and stripping a trailing .git.
Draft for maintainers, not for scrutineer operators. The title should be concise and non-alarmist. The body must explain:
location when presentsuggested_fix, mitigation, or rating when availableUse 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.
Write ./issue.md with the body, then run:
gh issue create --repo {owner}/{repo} --title "$TITLE" --body-file ./issue.mdPass 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.
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>"}Write ./report.json:
{
"upstream": "owner/repo",
"title": "Issue title",
"url": "https://github.com/owner/repo/issues/123",
"truncated": false,
"error": null
}On refusal or failure, write:
{
"error": "why nothing was filed"
}© 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
SKILL.md and 1 other file in skills/public-issue of alpha-omega-security/scrutineer.
Open the folder on GitHubat commit f3407bf
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Public Issue this skillalpha-omega-security/scrutineer | 239 | — | ~1.3k | Automated safety check: Pass | MIT | |
| ReleaseZeecka/AperiSolve | 852 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Triage Codeqlnetdata/netdata | 81k | — | ~1.8k | Automated safety check: Notes | GPL-3.0 | |
| Security AdvisoryMidnightBSD/src | 114 | — | ~2.2k | Automated safety check: Pass | Custom licence | |
| Security Vulnerability Analysiseclipse-ankaios/ankaios | 125 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Agentic GitHub Actions Auditortrailofbits/skills | 7.4k | 6 repos | ~5.4k | Automated safety check: Notes | CC-BY-SA-4.0 |
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.
netdata/netdata
Inspect, review or triage GitHub Code Scanning alerts, including CodeQL findings; apply verified dismissals when authorized.
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…
eclipse-ankaios/ankaios
Analyze potential Ankaios security vulnerabilities from pasted reports, local evidence, or advisory URLs.
trailofbits/skills
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.
openclaw/clawscan
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…
alpha-omega-security/scrutineer
Default pipeline scrutineer runs when a repository is added.
alpha-omega-security/scrutineer
Audit GitHub Actions workflows with zizmor and explain reported hits using bundled trust-boundary references.
alpha-omega-security/scrutineer
Run bandit against the Python source in the repository and map its hits into the findings shape.
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.
alpha-omega-security/scrutineer
Run git-pkgs list and sbom against the repository and emit one envelope with per-section status.
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.
Works with
Categories
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.
Public Issue fits situations like: defence-in-depth misses; other bugs that do not warrant coordinated private disclosure.
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.
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.
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.
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..
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.
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.
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.
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.
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.
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.