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/outfitter-dev/carabiner/agents-mdgit clone --depth 1 https://github.com/outfitter-dev/carabinerWrote 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/outfitter-dev/carabiner/agents-md)<a href="https://agentmods.dev/instructions/outfitter-dev/carabiner/agents-md"><img src="https://agentmods.dev/badge/instructions/outfitter-dev/carabiner/agents-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.02127 | $0.02127 |
| Opus 5 | $0.01064 | $0.01064 |
| Sonnet 5 | $0.00425 | $0.00425 |
| Haiku 4.5 | $0.00213 | $0.00213 |
Grade A, and why
carabiner 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 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Current Work:
- Provider adapter rollout:
.agents/notes/hook-adapter-architecture.md- Logger & fixture plan (unified logger, fixtures, docs, lefthook):
.agents/notes/logger-and-tests-plan.md
About Matt
- Name: Matt Galligan
- "Matt" for short
@galliganon GitHub
- Profile:
- Full-stack product builder who leverages (and depends on) AI agents
- Working on "Outfitter"
- Relevant links:
- Github: https://github.com/galligan
- X/Twitter: https://x.com/mg
Technology Stack
I default to using TypeScript (via Bun) for most projects. Where speed is a priority, I'll use Rust. Simply put, use the best tool for the job.
TypeScript
- Preference: Strongly typed (strict settings)
- Runtime: Bun
- Package Manager: Bun
- Server: Hono preferred, Express, Fastify, etc.
Rust
- Preference: Speed, performance, and safety
- Runtime: Rust
- Package Manager: Cargo
- Server: Axum, Actix, etc.
Frontends
- Framework: React + TanStack Router/TanStack Start or Next.js
- CSS/Styling: Tailwind CSS 4
- Components: shadcn/ui, components stored in
packages/ui/components- DRY, reusable, and accessible components
Database
- Starting Projects: SQLite by default (use Bun.SQL if TypeScript)
- Production: PostgreSQL (with Supabase or Neon) or Convex
- Redis Alternative: Upstash when relevant
API Design
- Preference Order: tRPC > REST > GraphQL
- Requirements: OpenAPI + Swagger documentation
- Priority: MCP server compatibility
Deployment
- Primary: Cloudflare preferred, Vercel
- Alternatives: Open to Fly.io
Testing
- Frameworks: Vitest, Playwright
- Priority: Compatibility with MCP servers for agent automation
Authentication
- Primary: BetterAuth
- Alternative: Clerk
CI/CD
- Primary: GitHub Actions (complex actions with Cloudflare runners)
- Alternative: Vercel/Cloudflare integrated CI when deploying there
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 · 233 lines · 2,127 tokens per session scan A 56985b229131
carabiner AGENTS.md is an instructions file published in the GitHub repository outfitter-dev/carabiner (4 stars, last pushed 7mo ago), licensed MIT. It adds 2,127 tokens to every session, about $0.0106 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-31.
Other instructions, from other repositories
cc-safe-setup CLAUDE.md
Claude Code instructions for yurukusa/cc-safe-setup, covering project rules, safety, code style and git.
Throughline CLAUDE.md
Claude Code instructions for kitepon/Throughline, covering claude.md, プロジェクト概要, 必読ドキュメント, 実装済みファイルの役割 and コア.
claude-hangar CLAUDE.md
Claude Code instructions for claude-hangar/claude-hangar, covering claude hangar — project instructions, what is this?, repository structure, language & communication and quality standards.
conclaude CLAUDE.md
Claude Code instructions for connerohnesorge/conclaude, covering you are the orchestrator, your role: master orchestrator, your mandatory workflow, step 1: analyze & plan (you do this) and step 2: delegate to subagents (one todo at a time).
cc-agents-kit CLAUDE.md
Claude Code instructions for AndrewDongminYoo/cc-agents-kit, covering claude.md, what this repo is, commands, layout contract and hook contract.
claude-code-notifire CLAUDE.md
Claude Code instructions for faustoFF/claude-code-notifire, covering claude.md, language, what this is, commands and architecture.