Gentleman.Dots is a personal development-environment configuration for Neovim, shells, terminal multiplexers, terminal emulators, and related command-line tools. Developers use it to install and configure a consistent coding setup, with an AI development layer managed separately through gentle-ai. The catalogue skills and instruction belong to that configured AI workflow.
Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/skills/gentleman-programming/gentleman.dots/gentleman-e2e)<a href="https://agentmods.dev/skills/gentleman-programming/gentleman.dots/gentleman-e2e"><img src="https://agentmods.dev/badge/skills/gentleman-programming/gentleman.dots/gentleman-e2e.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.1 | $0.00042 | $0.02029 |
| Opus 5 | $0.00021 | $0.01014 |
| Sonnet 5 | $0.00008 | $0.00406 |
| Haiku 4.5 | $0.00004 | $0.00203 |
Grade D, and why
gentleman-e2e scanned grade D with 3 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 7d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
git curl sudo build-essential \ Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
&& rm -rf /var/lib/apt/lists/* Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
git curl sudo build-essential \ How it starts
The opening of the file, as written. The whole thing — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
Use this skill when:
- Adding E2E tests for new features
- Creating Dockerfiles for new platforms
- Modifying the E2E test script
- Debugging installation failures
- Adding backup/restore test coverage
Critical Patterns
Pattern 1: Test Script Structure
All E2E tests in e2e_test.sh follow this pattern:
# Colors
RED='\033[0;31m'
GREEN='\033[0;32m'
YELLOW='\033[1;33m'
NC='\033[0m'
# Logging functions
log_test() { printf "${YELLOW}[TEST]${NC} %s\n" "$1"; }
log_pass() { printf "${GREEN}[PASS]${NC} %s\n" "$1"; PASSED=$((PASSED + 1)); }
log_fail() { printf "${RED}[FAIL]${NC} %s\n" "$1"; FAILED=$((FAILED + 1)); }
# Test function pattern
test_feature_name() {
log_test "Description of what we're testing"
if some_condition; then
log_pass "What passed"
else
log_fail "What failed"
fi
}
Pattern 2: Dockerfile Structure
Each platform has a Dockerfile in e2e/:
FROM ubuntu:22.04
# Install base dependencies
RUN apt-get update && apt-get install -y \
git curl sudo build-essential \
&& rm -rf /var/lib/apt/lists/*
# Create test user (non-root)
RUN useradd -m -s /bin/bash testuser && \
echo "testuser ALL=(ALL) NOPASSWD:ALL" >> /etc/sudoers
# Copy installer binary
COPY gentleman-installer-linux-amd64 /usr/local/bin/gentleman-dots
RUN chmod +x /usr/local/bin/gentleman-dots
# Copy test script
COPY e2e/e2e_test.sh /home/testuser/e2e_test.sh
RUN chmod +x /home/testuser/e2e_test.sh
USER testuser
WORKDIR /home/testuser
# Run tests
CMD ["./e2e_test.sh"]
Pattern 3: Non-Interactive Mode Testing
E2E tests use --non-interactive flag:
test_fish_tmux_nvim() {
log_test "Install: Fish + Tmux + Nvim"
if GENTLEMAN_VERBOSE=1 gentleman-dots --non-interactive \
--shell=fish --wm=tmux --nvim --backup=false 2>&1; then
# Verify fish config exists
if [ -f "$HOME/.config/fish/config.fish" ]; then
log_pass "Fish config was created"
else
log_fail "Fish config not found"
return
fi
# Verify nvim config exists
if [ -d "$HOME/.config/nvim" ]; then
log_pass "Neovim config directory created"
else
log_fail "Neovim config directory not found"
fi
else
log_fail "Installation failed"
fi
}
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.
- 7d ago First seen · 304 lines · 42 tokens per session scan D fe0480be26ec
gentleman-e2e is a skill published in the GitHub repository Gentleman-Programming/Gentleman.Dots (1,951 stars, last pushed 3d ago), licensed Apache-2.0. It adds 42 tokens to every session and 2,029 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
trailblaze
Use when working with Trailblaze — natural-language device control for coding agents across iOS, Android, and web, with replayable .trail.yaml files as the artifact. Trigger on mentions of Trailblaze, the trailblaze CLI, .trail.yaml files, trailmaps, waypoints, or requests to drive / author / debug / run UI tests on…
Detox Mobile Testing
Gray-box end-to-end testing for React Native apps with Detox. Covers .detoxrc.js configuration, build and test commands, matchers, device.launchApp control, automatic synchronization, and macOS CI pipelines.