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 issue-creationgit 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/issue-creation)<a href="https://agentmods.dev/skills/gentleman-programming/gentle-ai/issue-creation"><img src="https://agentmods.dev/badge/skills/gentleman-programming/gentle-ai/issue-creation/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/issue-creation"><img src="https://agentmods.dev/badge/skills/gentleman-programming/gentle-ai/issue-creation.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.00030 | $0.02680 |
| Opus 5.5 | $0.00012 | $0.01072 |
| Sonnet 5.5 | $0.00006 | $0.00536 |
| Haiku 4.5 | $0.00003 | $0.00268 |
Grade A, and why
issue-creation 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 16d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Creation
Activation Contract
Use this skill for drafting, creating, commenting on, triaging, or approving GitHub issues. Repository policy and selected YAML Issue Form are authoritative.
Hard Rules
- Reuse verified current-session facts; discover only missing or stale facts.
- Before any needed target policy read or write, resolve the exact target as
[HOST/]OWNER/REPO. Never assume the current repository. - YAML Issue Forms are the single format authority. Never use Markdown, a blank body, an alternate publisher, or a browser route as a fallback.
- Complete one open-and-closed duplicate search before a write. Reuse that result while it remains current.
- Never invent facts, selections, affirmations, labels, approval, or policy; ask for the smallest missing fact.
- Create-time labels are limited to labels declared by the selected form, discovered to exist, and permitted for the actor.
- Before ANY post-publication workflow mutation, read
references/delegated-workflow-actions.mdcompletely and follow it. It is normative, not optional background. - Require a current direct human instruction binding exact
HOST,REPO=OWNER/REPO, issue/PR number, and add/remove action. For other workflow actions, bind the exact action and target likewise. - Protected policy labels are
status:approved,size:exception, and any repository-defined gate-override/authorization label. Do not require separate target-host proof of the instructing human's identity. - Adding or removing a protected label requires authenticated actor target-host
viewerPermissionMAINTAINorADMINimmediately before mutation;TRIAGEnever suffices.size:exceptionalso needs a documented over-budget rationale and human choice to accept the exception; unknown gate labels stop. Verify target-host capability; for ordinary generic actions only,TRIAGEpermits only GitHub-granted existing-label and issue/PR close/reopen actions—not push/merge/label creation/deletion/administration. - Reject inferred/model-authored authority; atomic
status:approved, exactly one attempt/readback; fail closed. - Keep all body-bearing data in private temporary files outside repositories. Do not print the contents of any protected file.
- Make one create or comment attempt with no blind retry. Classify it exactly
confirmed | no_write | unknown;unknownstops every later mutation and retry.
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.
- 16d ago Changed · +12 lines 87b668d1635f
- 24d ago Changed 3ce49f8d1f1b
- 1mo ago First seen · 114 lines · 30 tokens per session scan A 99beff12891c
issue-creation is a skill published in the GitHub repository Gentleman-Programming/gentle-ai (7,864 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 2,680 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
jira
Unified Jira entry point. Routes to preview (default), create, or review subcommands.
revert
Git-aware revert that understands Draft tracks, phases, and tasks. Safely undo work at task, phase, or track level. Use when the user asks to 'revert this track', 'undo a phase', 'revert task X', or says 'roll back the last task', 'undo this work'.
standup
Generate standup summary from git history, track progress, and Jira/GitHub activity. Read-only — makes no changes to the codebase.
status
Display current progress of Draft tracks and active tasks. Shows phases, completion percentages, and blocked items.
integrations
Canonical integrations parent command. Handles external system exports and syncs. Routes intent to jira-preview or jira-create based on context.
ops
Primary router for operations, deployment, incident, and lifecycle workflows. Analyzes intent and dispatches to deploy-checklist, incident-response, standup, status, revert. Use for pre-deploy verification, handling outages, daily summaries, progress checks, and safe rollbacks.