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/spaquet/gemtracker/claude-mdgit clone --depth 1 https://github.com/spaquet/gemtrackerWrote 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/spaquet/gemtracker/claude-md)<a href="https://agentmods.dev/instructions/spaquet/gemtracker/claude-md"><img src="https://agentmods.dev/badge/instructions/spaquet/gemtracker/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.02613 | $0.02613 |
| Opus 5 | $0.01307 | $0.01307 |
| Sonnet 5 | $0.00523 | $0.00523 |
| Haiku 4.5 | $0.00261 | $0.00261 |
Grade A, and why
gemtracker 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 5d 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 — 320 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gemtracker Development Guide
Project Overview
Gemtracker is an interactive Terminal User Interface (TUI) written in Go that analyzes Ruby gem dependencies from Gemfile.lock files. It helps developers identify security risks, outdated dependencies, version conflicts, and provides comprehensive dependency analysis for Ruby, Rails, and other Ruby-based projects.
Purpose & Vision
The tool provides developers with quick, actionable insights into their gem dependencies through an intuitive interactive interface. Instead of manually parsing Gemfile.lock or running multiple separate commands, developers get a unified view of:
- First-level gems (directly installed dependencies) with version info and availability of updates
- Full dependency tree showing which gems depend on other gems
- Vulnerability detection with pointers to affected gems
- Search functionality to find gems and their usage across the project
Technology Stack
- Language: Go 1.24.0
- TUI Framework: BubbleTea (charmbracelet/bubbletea) for interactive terminal UI
- Dependencies:
charmbracelet/bubbles- Reusable components for BubbleTeacharmbracelet/lipgloss- Terminal styling and rendering
Architecture
Directory Structure
gemtracker/
├── cmd/gemtracker/ # Application entry point
│ └── main.go # CLI bootstrap and TUI initialization
├── internal/
│ ├── gemfile/ # Gemfile.lock parsing and analysis logic
│ │ ├── parser.go # Parse Gemfile.lock format
│ │ ├── analyzer.go # Analyze dependencies and relationships
│ │ ├── dependencies.go # Dependency tree data structures
│ │ ├── outdated.go # Check for newer versions available
│ │ └── vulnerabilities.go # CVE detection and reporting
│ └── ui/ # BubbleTea TUI components
│ ├── model.go # Root BubbleTea model and state management
│ ├── update.go # Message handling and state updates
│ ├── view.go # Rendering logic for all screens
│ └── styles.go # Terminal colors, fonts, spacing
└── go.mod # Go module definition
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.
- 5d ago First seen · 320 lines · 2,613 tokens per session scan A 1719ce900219
gemtracker CLAUDE.md is an instructions file published in the GitHub repository spaquet/gemtracker (22 stars, last pushed 4d ago), licensed MIT. It adds 2,613 tokens to every session, about $0.0131 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.
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.
gorest AGENTS.md
AGENTS.md instructions for pilinux/gorest, covering agents.md, project overview, build and run commands, build and tidy dependencies.
pvetui AGENTS.md
AGENTS.md instructions for devnullvoid/pvetui, covering agent instructions, initial setup, development workflow, quick reference and code quality standards.
kessoku AGENTS.md
AGENTS.md instructions for mazrean/kessoku, covering repository guidelines — kessoku, project structure, common commands, build and test.