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/bang9/ai-tools/claude-mdgit clone --depth 1 https://github.com/bang9/ai-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/bang9/ai-tools/claude-md)<a href="https://agentmods.dev/instructions/bang9/ai-tools/claude-md"><img src="https://agentmods.dev/badge/instructions/bang9/ai-tools/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.01497 | $0.01497 |
| Opus 5 | $0.00749 | $0.00749 |
| Sonnet 5 | $0.00299 | $0.00299 |
| Haiku 4.5 | $0.00150 | $0.00150 |
Grade C, and why
ai-tools CLAUDE.md scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
├── install.sh # One-liner install script (curl | bash) Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
├── install.sh # One-liner install script (curl | bash) How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ai-tools Development Guidelines
Project Overview
This repository contains tools for Claude Code to operate more efficiently. Each tool is a separate module under its own directory.
Cross-tool shared code lives under shared/ and should stay domain-neutral instead of absorbing tool-specific workflows.
Release Policy
Binary Distribution
All tools with compiled binaries MUST provide pre-built binaries for users without build tools installed.
Supported Platforms:
darwin-arm64(macOS Apple Silicon)darwin-amd64(macOS Intel)linux-amd64(Linux x86_64)windows-amd64(Windows x86_64)
Version Management
- Tag format:
v<MAJOR>.<MINOR>.<PATCH>(e.g.,v1.2.0) - All tools share the same version and are released together
ensure-binary.shandinstall.shfetch the latest version from GitHub API- Plugin
versionfields are auto-updated by CI on release
Release Process
- Commit changes
- Create and push tag:
git tag v1.x.x && git push --tags release.ymlorchestrates:- N product workflows build binaries and attach to GitHub Release
cc-marketplace-release.ymlupdatesplugin.jsonversions + regeneratesmarketplace.json+ auto-commits to main
CI/CD
Workflow Structure
.github/workflows/
├── release.yml # Orchestrator (tag v* trigger)
├── <tool>-release.yml # Product build (reusable, called by release.yml)
├── cc-marketplace-release.yml # Version + marketplace sync (reusable, called by release.yml)
├── <tool>-test.yml # Test workflow (push to main + PRs, path-filtered)
└── .github/scripts/
└── sync-marketplace.sh # Generates marketplace.json from plugin.json files
Orchestrator (release.yml):
- Triggers on tag push matching
v* - Calls all
<tool>-release.ymlworkflows in parallel - Then calls
cc-marketplace-release.ymlto sync versions
Product release (<tool>-release.yml):
- Triggered via
workflow_callwithversioninput - Builds cross-platform binaries and attaches to GitHub Release
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 · 146 lines · 1,497 tokens per session scan C 651e562c1a9f
ai-tools CLAUDE.md is an instructions file published in the GitHub repository bang9/ai-tools (10 stars, last pushed 1mo ago), licensed MIT. It adds 1,497 tokens to every session, about $0.0075 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
Backlog.md AGENTS.md
AGENTS.md instructions for MrLesk/Backlog.md, covering read this first, simplicity-first implementation rules, ui descriptions, commands and development.
Backlog.md copilot-instructions.md
Copilot instructions for MrLesk/Backlog.md, covering ⚠️ important, commands, development, testing and configuration management.
agentrq AGENTS.md
AGENTS.md instructions for agentrq/agentrq, covering agentrq codebase notes, project layout, desktop app (desktop/), three traps that are invisible in source and running tests.
vibe-kanban AGENTS.md
Instructions for BloopAI/vibe-kanban, covering repository guidelines, project structure & module organization, crate-specific guides, managing shared types between rust and typescript and build, test, and development commands.
DaybydayCRM AGENTS.md
AGENTS.md instructions for Bottelet/DaybydayCRM, covering daybydaycrm agent guide, documentation map, project snapshot, architecture rules and keep controllers thin.
DaybydayCRM copilot-instructions.md
Copilot instructions for Bottelet/DaybydayCRM, covering copilot instructions for daybydaycrm, working defaults, testing defaults, repository patterns to respect and known pitfalls.