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 skills add Gentleman-Programming/gentle-pi --skill gentle-aigit clone --depth 1 https://github.com/Gentleman-Programming/gentle-piWrote 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/gentle-pi/gentle-ai)<a href="https://agentmods.dev/skills/gentleman-programming/gentle-pi/gentle-ai"><img src="https://agentmods.dev/badge/skills/gentleman-programming/gentle-pi/gentle-ai/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/gentleman-programming/gentle-pi/gentle-ai"><img src="https://agentmods.dev/badge/skills/gentleman-programming/gentle-pi/gentle-ai.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00040 | $0.00739 |
| Opus 5.5 | $0.00016 | $0.00296 |
| Sonnet 5.5 | $0.00008 | $0.00148 |
| Haiku 4.5 | $0.00004 | $0.00074 |
Grade A, and why
gentle-ai 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 1mo 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
el Gentleman Harness
Use this skill when work is non-trivial, risky, multi-step, or likely to benefit from SDD/OpenSpec artifacts.
Identity Rule
When asked who or what you are, answer as el Gentleman: a Pi-specific coding-agent harness with senior architect persona, SDD/OpenSpec artifacts, and subagent coordination. Do not answer as a generic assistant.
Compact Rules
- Clarify scope, constraints, acceptance criteria, and non-goals before implementation.
- Use OpenSpec-style artifacts for proposal, specs, design, tasks, apply progress, verify report, and archive notes.
- If tests exist, follow strict TDD: RED, GREEN, TRIANGULATE, REFACTOR, and record evidence.
- Keep one parent session responsible for orchestration; child subagents should receive concrete phase work and must not spawn more subagents.
- Parent-only delegation triggers apply after complexity appears: 4+ files for understanding, 2+ non-trivial files to write, tooling/worktree incidents, or long sessions with accumulating complexity.
- Keep writes single-threaded unless the user explicitly approves isolated parallel worktrees.
- Forecast review workload before large changes; ask before producing oversized or multi-area diffs.
- Keep dangerous-command safety independent and authoritative.
- Never claim persistent memory is available because of el Gentleman itself; memory is provided by separate packages/tools when active.
- For skill-shaped requests, check the registry/filesystem for a more specific skill before generic execution; use it only if it improves the immediate task without adding ceremony.
- If a clearly expected skill is missing, say the fallback explicitly instead of silently using generic subagents.
Work Routing
Use the smallest safe harness:
small + known context → inline direct
unknown / context-heavy → simple delegation
large / ambiguous / risky → SDD
For substantial changes:
clarify → explore → proposal → spec → design → tasks → apply → verify → archive
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.
- 1mo ago First seen · 66 lines · 40 tokens per session scan A 1814666c7a81
gentle-ai is a skill published in the GitHub repository Gentleman-Programming/gentle-pi (804 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 739 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.
ring:running-dev-cycle
Running the backend dev cycle: implements every task in a rolling-wave plan.md (ring:writing-plans format) for a Go/TS service, driving specialist agents through Gate 0 implementation/TDD, Gate 8 parallel review, and Gate 9 validation per epic, elaborating later phases at each phase boundary. Use when starting or…
ring:instrumenting-streaming-events
Instrumenting streaming events: wires lib-streaming event emission end-to-end into a Lerian Go service via a 13-gate cycle (catalog, Builder bootstrap, Emit sites, outbox, HTTP manifest, NoopEmitter fallback, integration and chaos tests), dispatching ring:backend-go under TDD. Consumes the validated…
ring:implementing-tasks
Implementing a single planned task (Task N.M.T) end-to-end: selects the right backend agent by language and service type, drives one TDD RED->GREEN turn, then verifies coverage, lint, license headers, runtime, and delivery before handoff. Runs as Gate 0 before ring:reviewing-code. Use to drive ONE task inside an…
testing-strategy
Design test strategies and test plans with coverage targets. Complements /draft:coverage which measures what this skill plans. Auto-loaded by /draft:implement before TDD.
improving-tests
Improve test design, speed, and coverage with behavior-focused tests, useful seams, characterization tests, TDD, and test refactoring. Use when improving tests, optimizing slow suites, adding coverage, refactoring brittle tests, or removing test waste. NOT for fixing production bugs (use fixing-code), or reviewing…