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.
npx skills add Gentleman-Programming/gentle-ai --skill skill-creatorgit 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/skills/gentleman-programming/gentle-ai/skill-creator)<a href="https://agentmods.dev/skills/gentleman-programming/gentle-ai/skill-creator"><img src="https://agentmods.dev/badge/skills/gentleman-programming/gentle-ai/skill-creator/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-ai/skill-creator"><img src="https://agentmods.dev/badge/skills/gentleman-programming/gentle-ai/skill-creator.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.00027 | $0.00916 |
| Opus 5.5 | $0.00011 | $0.00366 |
| Sonnet 5.5 | $0.00005 | $0.00183 |
| Haiku 4.5 | $0.00003 | $0.00092 |
Grade A, and why
skill-creator 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Activation Contract
Create a skill when:
- A pattern is used repeatedly and AI needs guidance
- Project-specific conventions differ from generic best practices
- Complex workflows need step-by-step instructions
- Decision trees help AI choose the right approach
Do not create a skill when the pattern is trivial, one-off, or better served by normal documentation.
Hard Rules
- When working in this repo, first follow
docs/skill-style-guide.mdas the normative source before creating or updating skills. - For installed global skills, use
references/skill-style-guide.mdas the bundled local copy of that guide whendocs/skill-style-guide.mdis unavailable. - If neither guide is available, use the compact inline rules below.
- A skill is a runtime instruction contract for an LLM, not human documentation.
- Do not add a
Keywordssection; preserve essential trigger words indescription. - References must point to local files.
- Keep the skill body concise: target 180–450 tokens, recommended max 700, hard max 1000.
Decision Gates
| Need | Action |
|---|---|
| Code templates, schemas, fixtures, generated examples | Put them in assets/ |
| Conceptual detail, edge cases, existing docs | Put local links in references/ |
Long explanation in SKILL.md |
Move it to a supporting file |
| Multiple meaningful paths | Add a compact decision table |
Execution Steps
- Check whether
docs/skill-style-guide.mdexists; if it does, apply it before the bundled local copy or inline fallback rules. - If the repo guide is unavailable, read
references/skill-style-guide.mdand apply it before the inline fallback rules. - Confirm the skill does not already exist and the pattern is reusable.
- Create or update
skills/{skill-name}/SKILL.mdusing this required structure:
skills/{skill-name}/
├── SKILL.md # Required - main skill file
├── assets/ # Optional - templates, schemas, examples
│ ├── template.py
│ └── schema.json
└── references/ # Optional - links to local docs
└── docs.md # Points to docs/developer-guide/*.mdx
- Use this frontmatter shape:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 105 lines · 27 tokens per session scan A 2e560aec25d3
skill-creator is a skill published in the GitHub repository Gentleman-Programming/gentle-ai (7,884 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 916 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 skills, from other repositories
new-track
Start a new feature or bug track. Collaborative intake process with structured questions, AI guidance, and progressive refinement before generating spec.md and plan.md. Use when the user asks to 'start a new track', 'create a feature track', 'add a bug fix track', or says 'I want to build X', 'fix the Y bug', 'plan a…
jira
Unified Jira entry point. Routes to preview (default), create, or review subcommands.
coverage
Compute code coverage for active track or module. Targets 95%+ coverage with report and justification for uncovered lines. Complements TDD workflow.
adr
Create and manage Architecture Decision Records. Documents significant technical decisions with context, alternatives, and consequences. Also supports evaluate (assess proposals) and design (system design) modes.
deploy-checklist
Pre-deployment verification checklist. Generates customized checklists based on tech-stack with rollback triggers. Auto-invoked by /draft:upload.
change
Handle mid-track requirement changes. Analyzes impact on completed and pending tasks, proposes amendments to spec.md and plan.md before applying.