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/agents-mdgit clone --depth 1 https://github.com/Allra-Fintech/git-issueWhat 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.01270 | $0.01270 |
| Opus 5 | $0.00635 | $0.00635 |
| Sonnet 5 | $0.00254 | $0.00254 |
| Haiku 4.5 | $0.00127 | $0.00127 |
Grade A, and why
git-issue AGENTS.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 2d 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 — 158 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).
Finding Issues
When a user references an issue like "#001" or "issue 001":
- Search for the file in
.issues/open/or.issues/closed/ - File naming pattern:
{id}-{slug}.md(e.g.,001-implement-git-issue-cli-tool.md) - Read the full issue file including YAML frontmatter and Markdown body
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.
- 2d ago First seen · 158 lines · 1,270 tokens per session scan A 39c352b749dd
git-issue AGENTS.md is an instructions file published in the GitHub repository Allra-Fintech/git-issue (11 stars, last pushed 6mo ago), licensed MIT. It adds 1,270 tokens to every session, about $0.0064 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
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.