It is for running the ghist post-tool-use command after Bash tool calls.

It records an automatic post-command action so it can happen consistently without manual invocation.

How unnecessary-special-projects/ghist configures Claude Code

ghist: Settings file for Claude Code

.claude/settings.json

ghist is a settings file for Claude Code from unnecessary-special-projects/ghist. Its token cost is not measured, scanned A, original, MIT.

A settings file that declares one hook, meaning an automatic action triggered after a tool runs. The hook runs a command after Bash commands are used.

In plain words

What is it for?: It is for running the ghist post-tool-use command after Bash tool calls.
Why use it?: It records an automatic post-command action so it can happen consistently without manual invocation.

Written for Claude Code: PostToolUse hook event.

This is unnecessary-special-projects/ghist's own configuration. It tells Claude Code how to work on ghist 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 ghist configures →

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/nxnze/_/ghist/ghist.

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 unnecessary-special-projects/ghist. 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/unnecessary-special-projects/ghist/main/.claude/settings.json

Clone the repo

git clone --depth 1 https://github.com/unnecessary-special-projects/ghist

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/settings/unnecessary-special-projects/ghist/settings/github.svg)](https://agentmods.dev/settings/unnecessary-special-projects/ghist/settings)

Your own site

<a href="https://agentmods.dev/settings/unnecessary-special-projects/ghist/settings"><img src="https://agentmods.dev/badge/settings/unnecessary-special-projects/ghist/settings/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/settings/unnecessary-special-projects/ghist/settings"><img src="https://agentmods.dev/badge/settings/unnecessary-special-projects/ghist/settings.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

ghist 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 2mo 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/settings.json · 16 lines

What it actually says

{
  "hooks": {
    "PostToolUse": [
      {
        "matcher": "Bash",
        "hooks": [
          {
            "type": "command",
            "command": "/Users/nxnze/_/ghist/ghist hook post-tool-use"
          }
        ]
      }
    ]
  }
}

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.

Hook PostToolUse 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.

2mo ago First seen · 16 lines scan A 6c391adb5a67

Subscribe to this mod's changes

ghist is a settings file published in the GitHub repository unnecessary-special-projects/ghist (174 stars, last pushed 8mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.

ghist next to 6 settings from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
ghistunnecessary-special-projects/ghist	Settings file	174	8mo ago	MIT	A	—	Claude Code
supabasesupabase/supabase	Settings file	115k	yesterday	Apache-2.0	A	—	Claude Code
supersetapache/superset	Settings file	75k	today	Apache-2.0	A	—	Claude Code
RuViewruvnet/RuView	Settings file	103k	yesterday	MIT	A	—	Claude Code
claude-cookbooksanthropics/claude-cookbooks	Settings file	54k	2d ago	MIT	A	—	Claude Code
ormprisma/orm	Settings file	48k	yesterday	Apache-2.0	A	—	Claude Code
claude-code-best-practiceshanraisshan/claude-code-best-practice	Settings file	69k	yesterday	MIT	A	—	Claude Code