Controlling Bash-based GitHub issue access through an automatic pre-command check.

It enforces a read-only rule for GitHub issues in the configured repository. The hook can stop unwanted changes before the command runs.

How piguo45/single-file-wbs configures Claude Code

single-file-wbs: Hook for Claude Code

.claude/settings.json

PreToolUse is a hook for Claude Code from piguo45/single-file-wbs. Its token cost is not measured, scanned A, original, MIT.

A PreToolUse hook configuration for Bash commands. Before each matching command, it runs a repository script named block-gh-issue-write.sh to prevent GitHub issue writes.

In plain words

What is it for?: Controlling Bash-based GitHub issue access through an automatic pre-command check.
Why use it?: It enforces a read-only rule for GitHub issues in the configured repository. The hook can stop unwanted changes before the command runs.

Written for Claude Code: $CLAUDE_PROJECT_DIR variable.

This is piguo45/single-file-wbs's own configuration. It tells Claude Code how to work on single-file-wbs 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 single-file-wbs configures →

One of 2 entries in settings.json upstream. Installing this one merges just its entry into your config; the other 1 are separate, each on its own page.

Reuse

Borrowing it

Nothing to install: this file belongs to piguo45/single-file-wbs. 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/piguo45/single-file-wbs/main/.claude/settings.json

Clone the repo

git clone --depth 1 https://github.com/piguo45/single-file-wbs

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.

README.md

[![agentmods](https://agentmods.dev/badge/hooks/piguo45/single-file-wbs/pre-tool-use/github.svg)](https://agentmods.dev/hooks/piguo45/single-file-wbs/pre-tool-use)

Your own site

<a href="https://agentmods.dev/hooks/piguo45/single-file-wbs/pre-tool-use"><img src="https://agentmods.dev/badge/hooks/piguo45/single-file-wbs/pre-tool-use/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.

Your own site · 80×15

<a href="https://agentmods.dev/hooks/piguo45/single-file-wbs/pre-tool-use"><img src="https://agentmods.dev/badge/hooks/piguo45/single-file-wbs/pre-tool-use.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

PreToolUse 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 commands this hook runs, not an audit. A hook is shell that executes on your machine at the event it names, which is why every command in it is printed with what was found.

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/settings.json · 15 lines

What it actually says

{
  "PreToolUse": [
    {
      "matcher": "Bash",
      "hooks": [
        {
          "type": "command",
          "command": "\"$CLAUDE_PROJECT_DIR\"/.claude/hooks/block-gh-issue-write.sh",
          "timeout": 5,
          "statusMessage": "gh issue は読み取り専用（リポ設定）"
        }
      ]
    }
  ]
}

Same file

What else `settings.json` configures

This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.

Settings file single-file-wbs A not measured

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.

1mo ago First seen · 15 lines scan A 520a444651e4

Subscribe to this mod's changes

PreToolUse is a hook published in the GitHub repository piguo45/single-file-wbs (131 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: a hook is shell that never enters the context. 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-09-13.

DevOps and cloud Project Management gantt gantt-chart inazuma japanese no-dependencies

PreToolUse next to 6 hooks from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
PreToolUsepiguo45/single-file-wbs	Hook	131	1mo ago	MIT	A	—	Claude Code
PostToolUseBene-2020/plane-codex-mcp	Hook	86	2d ago	MIT	A	—	Claude Code
SessionEndBene-2020/plane-codex-mcp	Hook	86	2d ago	MIT	A	—	Claude Code
PostToolUseoperately/operately	Hook	617	yesterday	none	A	—	Claude Code
PostCompactiLomer/Metho_agentic	Hook	5	21d ago	MIT	A	—	Claude Code
StopBene-2020/plane-codex-mcp	Hook	86	2d ago	MIT	A	—	Claude Code
PostToolUsesupabase/supabase	Hook	115k	yesterday	Apache-2.0	A	—	Claude Code