Gentle-AI configures an existing AI coding agent into an engineering environment with persistent memory, planning workflows, skills, tool servers, model routing, and optional review. Developers and teams use it to make coding agents follow project conventions and retain decisions across sessions. The catalogue entries are its skills, commands, agents, and instruction.
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.
git clone --depth 1 https://github.com/Gentleman-Programming/gentle-aiWrote 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/commands/gentleman-programming/gentle-ai/skill-registry)<a href="https://agentmods.dev/commands/gentleman-programming/gentle-ai/skill-registry"><img src="https://agentmods.dev/badge/commands/gentleman-programming/gentle-ai/skill-registry/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/commands/gentleman-programming/gentle-ai/skill-registry"><img src="https://agentmods.dev/badge/commands/gentleman-programming/gentle-ai/skill-registry.svg" alt="Reviewed on agentmods" width="80" 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.00014 | $0.00071 |
| Opus 5.5 | $0.00006 | $0.00028 |
| Sonnet 5.5 | $0.00003 | $0.00014 |
| Haiku 4.5 | $0.00001 | $0.00007 |
Grade A, and why
skill-registry 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.
What it actually says
Load skill-registry first, then rebuild the skill registry for the current project and configured skill directories.
Return the registry path, skill count, cache status, and whether Engram was updated.
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 · 10 lines · 14 tokens per session scan A d9ec9c7df455
skill-registry is a command published in the GitHub repository Gentleman-Programming/gentle-ai (8,012 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 71 once invoked, about $0.0001 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 commands, from other repositories
cross-critique
Adversarial multi-angle critique. All three auditors fire in parallel (codex=technical, gemini=strategic, claude=ux). Counter-args ranked by rebuttal survival score, not raw severity. Usage: /cross-critique [--with | list | compare].
pr-feedback-ingest
Turn PR feedback (Greptile, CI, bots, humans) into a traceable backlog, so the next step is a narrow implement-approved-slice. Corrective scope only. Use when a PR has review feedback to map to files and slices. Do not use for a new direction or contract (use post-review-pivot), no payload, or task-memory drift only…
layer-check
You are the Three-Layer Enforcement Agent, the strict validator that ensures every feature is REAL across all tiers: Database, Backend, and Frontend. You do not accept incomplete implementations.
review
You are a exacting code reviewer who combines high quality standards with deep technical expertise. You only flag issues that genuinely matter - bugs, security vulnerabilities, logic errors, and violations of framework standards.
certify
/certify Full certification (all 15 categories) /certify --category security Single category only /certify --html report.html Also generate HTML report.
coder
You are a rigorous senior software engineer operating as the Coder persona in the ColdStart workflow. You give honest, evidence-based assessments, never assume ambiguous requirements, and never sign off on sloppy or untested code. Your mission is to implement code only when feature specifications and security…