Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/allra-fintech/git-issue/claude-mdgit clone --depth 1 https://github.com/Allra-Fintech/git-issueWrote 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/allra-fintech/git-issue/claude-md)<a href="https://agentmods.dev/instructions/allra-fintech/git-issue/claude-md"><img src="https://agentmods.dev/badge/instructions/allra-fintech/git-issue/claude-md.svg" alt="Measured on agentmods" 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 | $0.01438 | $0.01438 |
| Opus 5 | $0.00719 | $0.00719 |
| Sonnet 5 | $0.00288 | $0.00288 |
| Haiku 4.5 | $0.00144 | $0.00144 |
Grade A, and why
git-issue 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
git-issue is a lightweight CLI tool written in Go for managing issues as Markdown files within git repositories. The tool provides AI agents and developers direct access to issue context without external integrations.
Architecture
Project Structure
git-issue/
├── cmd/gi/
│ └── main.go # Entry point
├── cmd/ # CLI commands (Cobra-based)
│ ├── root.go # Root command and global flags
│ ├── init.go # Initialize .issues/ directory
│ ├── create.go # Create new issues
│ ├── list.go # List/filter issues
│ ├── show.go # Display issue details
│ ├── close.go # Close issues (with --commit flag)
│ ├── open.go # Reopen issues (with --commit flag)
│ ├── edit.go # Edit issues in $EDITOR
│ └── search.go # Full-text search
├── pkg/
│ ├── issue.go # Core Issue struct and operations
│ ├── storage.go # File system operations (.counter, file I/O)
│ └── parser.go # YAML frontmatter + Markdown parsing
└── .issues/ # Issue storage (NOT in version control for this repo)
├── open/ # Open issues: {id}-{slug}.md
├── closed/ # Closed issues
├── .counter # Next issue ID
└── template.md # Template for new issues
Key Dependencies
github.com/spf13/cobra- CLI frameworkgopkg.in/yaml.v3- YAML frontmatter parsinggithub.com/fatih/color- Terminal colorsgithub.com/olekukonko/tablewriter- Table output formatting
Issue Management
This project uses its own issue tracking system (dogfooding).
Creating Issues
When creating a new issue, always use the gi create command instead of manually creating files:
# Create a new issue
gi create "Your issue title here"
# Create with assignee
gi create "Fix login bug" --assignee username
# Create with labels (can use multiple --label flags)
gi create "Add dark mode" --label feature --label frontend
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.
- 4d ago First seen · 182 lines · 1,438 tokens per session scan A adcf32bea5fa
git-issue CLAUDE.md is an instructions file published in the GitHub repository Allra-Fintech/git-issue (11 stars, last pushed 7mo ago), licensed MIT. It adds 1,438 tokens to every session, about $0.0072 per session on Opus 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.
Other instructions, from other repositories
ollama CLAUDE.md
Claude Code instructions for ollama/ollama: See AGENTS.md for the shared agent instructions for this repository.
azure-sdk-for-go go-code.instructions.md
Instructions for Azure/azure-sdk-for-go: All code should follow the guidelines from the Azure Go SDK Guidelines. This document is a summary of the most important guidelines to follow when contributing to the Azure Go SDK.
gorest AGENTS.md
AGENTS.md instructions for pilinux/gorest, covering agents.md, project overview, build and run commands, build and tidy dependencies.
chatgpt-cli CLAUDE.md
Claude Code instructions for kardolus/chatgpt-cli, covering chatgpt-cli — release runbook, prerequisites, 1. cut the release, 2. publish the github release + binaries and 3. update the homebrew tap.
kessoku AGENTS.md
AGENTS.md instructions for mazrean/kessoku, covering repository guidelines — kessoku, project structure, common commands, build and test.
ketch CLAUDE.md
Claude Code instructions for 1broseidon/ketch, covering ketch, architecture, build & test, output format and output flags (all commands).