zkbugs: Skill for Claude Code

.claude/skills/process-github-issue/SKILL.md

process-github-issue is a skill for Claude Code from zksecurity/zkbugs. It costs 42 tokens per session (269 once invoked), scanned A, original, MIT.

A workflow for turning a GitHub issue or pull request into an entry in the zkbugs dataset, which records vulnerabilities in zero-knowledge circuits.

In plain words
What is it for?
Use it to parse reports, create dataset files and configurations, find similar bugs, and run the Circom verification pipeline.
Why use it?
It provides a repeatable way to extract circuit bugs and check that Circom fixes or examples pass the required tests.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is zksecurity/zkbugs's own configuration. It tells Claude Code how to work on zkbugs itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything zkbugs configures →

Reuse

Borrowing it

Nothing to install: this file belongs to zksecurity/zkbugs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/zksecurity/zkbugs/main/.claude/skills/process-github-issue/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/zksecurity/zkbugs

Made for: Claude Code.

Wrote 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.

agentmods badge for process-github-issue

README.md
[![agentmods](https://agentmods.dev/badge/skills/zksecurity/zkbugs/process-github-issue/github.svg)](https://agentmods.dev/skills/zksecurity/zkbugs/process-github-issue)
Your own site
<a href="https://agentmods.dev/skills/zksecurity/zkbugs/process-github-issue"><img src="https://agentmods.dev/badge/skills/zksecurity/zkbugs/process-github-issue/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.

agentmods 80×15 button for process-github-issue

Your own site · 80×15
<a href="https://agentmods.dev/skills/zksecurity/zkbugs/process-github-issue"><img src="https://agentmods.dev/badge/skills/zksecurity/zkbugs/process-github-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 269 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00042 $0.00269
Opus 5.5 $0.00017 $0.00108
Sonnet 5.5 $0.00008 $0.00054
Haiku 4.5 $0.00004 $0.00027

Measured 1mo ago against content hash 317fd83d40c5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

process-github-issue 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 1mo 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.

.claude/skills/process-github-issue/SKILL.md · 23 lines

What it actually says

Process GitHub Issue/PR

Process the GitHub issue or pull request at $ARGUMENTS and extract all ZK circuit vulnerabilities into the zkbugs dataset.

Follow prompts/process_github_issue.md for Phase 1 (issue/PR parsing) and the summary (Phase 3.3-3.4); it forwards to prompts/_bug_processing.md for Phase 2 and the rest of Phase 3.

For Circom bugs, run the full verification pipeline in section 2.5 of _bug_processing.md (compile + setup + positive test + clean). The "finish the job" guidance, zkbugs_vars.sh handling, and TODO discipline all live in the shared prompt — do not leave TODOs unless you hit a genuine blocker.

Changes

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.

  1. 1mo ago First seen · 23 lines · 42 tokens per session scan A 317fd83d40c5

Subscribe to this mod's changes

process-github-issue is a skill published in the GitHub repository zksecurity/zkbugs (351 stars, last pushed 27d ago), licensed MIT. It adds 42 tokens to every session and 269 once invoked, about $0.0002 per session on Opus 5.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-08-30.