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/gentleman-programming/gentleman.dots/agents-mdgit clone --depth 1 https://github.com/Gentleman-Programming/Gentleman.DotsWrote 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/gentleman-programming/gentleman.dots/agents-md)<a href="https://agentmods.dev/instructions/gentleman-programming/gentleman.dots/agents-md"><img src="https://agentmods.dev/badge/instructions/gentleman-programming/gentleman.dots/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.02709 | $0.02709 |
| Opus 5 | $0.01354 | $0.01354 |
| Sonnet 5 | $0.00542 | $0.00542 |
| Haiku 4.5 | $0.00271 | $0.00271 |
Grade A, and why
Gentleman.Dots 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gentleman.Dots AI Agent Skills
Single Source of Truth - This file is the master for all AI assistants. Run
./skills/setup.shto sync to Claude, Gemini, Copilot, and Codex formats.
This repository provides AI agent skills for Claude Code, OpenCode, and other AI assistants. Skills provide on-demand context and patterns for working with this codebase.
Quick Start
When working on this project, Claude Code automatically loads relevant skills based on context. For manual loading, read the SKILL.md file directly.
Available Skills
Gentleman.Dots Specific (Repository Skills)
| Skill | Description | File |
|---|---|---|
gentleman-bubbletea |
Bubbletea TUI patterns, Model-Update-View, screen navigation | SKILL.md |
gentleman-trainer |
Vim Trainer RPG system, exercises, progression, boss fights | SKILL.md |
gentleman-installer |
Installation steps, interactive/non-interactive modes | SKILL.md |
gentleman-e2e |
Docker-based E2E testing, multi-platform validation | SKILL.md |
gentleman-system |
OS detection, command execution, cross-platform support | SKILL.md |
go-testing |
Go testing patterns, table-driven tests, Bubbletea testing | SKILL.md |
Note: User-facing AI skills (React 19, TypeScript, SDD workflow, etc.) are now managed by gentle-ai.
Auto-invoke Skills
When performing these actions, ALWAYS invoke the corresponding skill FIRST:
| Action | Invoke First | Why |
|---|---|---|
| Adding new TUI screen | gentleman-bubbletea |
Screen constants, Model state, Update handlers |
| Creating Vim exercises | gentleman-trainer |
Exercise structure, module registration, validation |
| Adding installation step | gentleman-installer |
Step registration, OS handling, error wrapping |
| Writing E2E tests | gentleman-e2e |
Test structure, Docker patterns, verification |
| Adding OS support | gentleman-system |
Detection priority, command execution patterns |
| Writing Go tests | go-testing |
Table-driven tests, teatest patterns |
| Creating new skill | skill-creator |
Skill structure, naming, frontmatter |
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 · 220 lines · 2,709 tokens per session scan A 8a124183e7fa
Gentleman.Dots AGENTS.md is an instructions file published in the GitHub repository Gentleman-Programming/Gentleman.Dots (1,944 stars, last pushed 7d ago), licensed Apache-2.0. It adds 2,709 tokens to every session, about $0.0135 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.