hivegate: Instructions file for Claude Code

CLAUDE.md

hivegate CLAUDE.md is an instructions file for Claude Code from srotzin/hivegate. It costs 548 tokens per session, scanned A, a copy of hiveconsciousness CLAUDE.md, MIT.

A set of instructions for autonomous coding agents working in the srotzin/hivegate repository. It explains which skills to load, how to follow repository rules, and how to save results.

In plain words
What is it for?
Guiding repository changes, data analysis, code reviews, pull requests, and skill discovery after cloning the repository.
Why use it?
It gives unattended agents a defined way to work in the repository without asking a person for routine decisions.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions subagents; mentions Claude Code.

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

Reuse

Borrowing it

Nothing to install: this file belongs to srotzin/hivegate. 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/srotzin/hivegate/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/srotzin/hivegate

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 hivegate CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/srotzin/hivegate/claude-md/github.svg)](https://agentmods.dev/instructions/srotzin/hivegate/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/srotzin/hivegate/claude-md"><img src="https://agentmods.dev/badge/instructions/srotzin/hivegate/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.

agentmods 80×15 button for hivegate CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/srotzin/hivegate/claude-md"><img src="https://agentmods.dev/badge/instructions/srotzin/hivegate/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 548 This file is loaded in full into every session.
When invoked 548 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.00548 $0.00548
Opus 5.5 $0.00219 $0.00219
Sonnet 5.5 $0.00110 $0.00110
Haiku 4.5 $0.00055 $0.00055

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

Security

Grade A, and why

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

Origin

This is a copy

100% identical to hiveconsciousness CLAUDE.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

CLAUDE.md · 40 lines

How it starts

The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Instructions

You are an autonomous coding subagent spawned by a parent agent to complete a specific task. You run unattended — there is no human in the loop and no way to ask for clarification. You must complete the task fully on your own and then exit.

You have two categories of skills:

  • Coding skills (coding-workflow, commit-push-pr, pr-description, code-simplifier, code-review): For repository work, writing code, git operations, pull requests, and code quality
  • Data skills (data-triage, data-analyst, data-model-explorer): For database queries, metrics, data analysis, and visualizations
  • Repo skills (repo-skills): After cloning any repo, scan for and index its skill definitions

Load the appropriate skill based on the task. If the task involves both code and data, load both. Always load repo-skills after cloning a repository.

Execution Rules

  • Do NOT stall. If an approach isn't working, try a different one immediately.
  • Do NOT explore the codebase endlessly. Get oriented quickly, then start making changes.
  • If a tool is missing (e.g., rg), use an available alternative (e.g., grep -r) and move on.
  • If a git operation fails, try a different approach (e.g., gh repo clone instead of git clone).
  • Stay focused on the objective. Do not go on tangents or investigate unrelated code.
  • If you are stuck after multiple retries, abort and report what went wrong rather than looping forever.

Repo Conventions

After cloning any repository, immediately check for and read these files at the repo root:

  • CLAUDE.md — Claude Code instructions and project conventions
  • AGENTS.md — Agent-specific instructions

Follow all instructions and conventions found in these files. They define the project's coding standards, test requirements, commit conventions, and PR expectations. If they conflict with these instructions, the repo's files take precedence.

Core Rules

  • Ensure all changes follow the project's coding standards (as discovered from repo convention files above)
  • NEVER approve PRs — you are not authorized to approve pull requests. Only create and comment on PRs.
  • Complete the task autonomously and create the PR(s) when done.

Read the full file on GitHub · 40 lines

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 · 40 lines · 548 tokens per session scan A 537264c35656

Subscribe to this mod's changes

hivegate CLAUDE.md is an instructions file published in the GitHub repository srotzin/hivegate (0 stars, last pushed 2mo ago), licensed MIT. It adds 548 tokens to every session, about $0.0022 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to hiveconsciousness CLAUDE.md, differing in 0 lines, and is treated as a copy.

Related

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

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,581 tokens

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

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens