Borrowing it
Nothing to install: this file belongs to gmhelmold/HuGR_Tools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/gmhelmold/HuGR_Tools/main/CLAUDE.mdgit clone --depth 1 https://github.com/gmhelmold/HuGR_ToolsWrote 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.
[](https://agentmods.dev/instructions/gmhelmold/hugr_tools/claude-md)<a href="https://agentmods.dev/instructions/gmhelmold/hugr_tools/claude-md"><img src="https://agentmods.dev/badge/instructions/gmhelmold/hugr_tools/claude-md/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.
<a href="https://agentmods.dev/instructions/gmhelmold/hugr_tools/claude-md"><img src="https://agentmods.dev/badge/instructions/gmhelmold/hugr_tools/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00454 | $0.00454 |
| Opus 5.5 | $0.00182 | $0.00182 |
| Sonnet 5.5 | $0.00091 | $0.00091 |
| Haiku 4.5 | $0.00045 | $0.00045 |
Grade A, and why
HuGR_Tools CLAUDE.md 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.
What it actually says
CLAUDE.md — repo working notes for AI agents
Monorepo of 37 MCP toolkit Cloudflare Workers on a shared @hugr/kernel. Remote: HumanGuardrail/HuGR_Tools.
Overview
- Auth: pluggable
IdentityProvider, fail-closed. The kernel resolves its mode strongest-first — RS256 → HMAC → remote introspection (packages/kernel/src/identity/hugr-auth.ts). A self-hoster needs onlyHUGR_INLINE_HMAC_SECRET(local HS256 verification, no network call). Scopes are derived server-side from the caller's plan, never read from the token. - BYOK: workers store no provider key; callers send provider creds as per-request headers; fail-closed.
- CI: GitHub-hosted (
ubuntu-latest);ci.ymlruns the workspace test suite. Reference figures: 8,538 passed / 1,928 credential-gated skips / 0 failed. - Deploy: each package is a standard Cloudflare Worker —
wrangler devlocally, orwrangler deploy --env <env>to your own account. The committedwrangler.tomlvalues (account_id, introspect URL) are placeholders — fill in your own.
Conventions
- Worker names come from each
packages/<pkg>/wrangler.toml[env.<env>].name— NOT alwayshugr-<pkg>-<env>(the Datadog bundles arehugr-datadog-{logs,monitors,dashboards}-<env>). Never derive a worker name from the package name; read the toml. - Secrets never go in the repo or in chat. Real provider tokens live in GitHub Secrets / your machine, not committed.
zodis v4 across the workspace (v3→v4 gotchas: 1-argz.record→ 2-arg,.default({})→.prefault({}), andz.unknown()object fields need explicit.optional()).- Use PRs (squash) off
main; CI must be green.
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 · 18 lines · 454 tokens per session scan A 34ac3293a410
HuGR_Tools CLAUDE.md is an instructions file published in the GitHub repository gmhelmold/HuGR_Tools (0 stars, last pushed 3mo ago), licensed MIT. It adds 454 tokens to every session, about $0.0018 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-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.