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 skill-creatorgit 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/skill-creator)<a href="https://agentmods.dev/skills/gentleman-programming/gentle-pi/skill-creator"><img src="https://agentmods.dev/badge/skills/gentleman-programming/gentle-pi/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-pi/skill-creator"><img src="https://agentmods.dev/badge/skills/gentleman-programming/gentle-pi/skill-creator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 86 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00037 | $0.00728 |
| Opus 5.5 | $0.00015 | $0.00291 |
| Sonnet 5.5 | $0.00007 | $0.00146 |
| Haiku 4.5 | $0.00004 | $0.00073 |
Grade A, and why
gentle-ai-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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Activation Contract
Use this skill when creating or updating a reusable AI skill for Pi or another agent runtime.
Create a skill when:
- a workflow or convention is reused across sessions;
- generic agent behavior needs project-specific constraints;
- a decision tree helps the agent choose safely;
- examples, templates, or references would make future execution more reliable.
Do not create a skill for a one-off task, generic documentation, or rules that belong in code/tests.
Hard Rules
- Follow
docs/skill-style-guide.mdas the normative source for skill structure and style. - A skill is an LLM runtime contract, not human-facing docs.
- Keep
SKILL.mdconcise: target 180–450 tokens, max 1000. - Use imperative instructions and concrete gates; avoid tutorials and background prose.
- Frontmatter
descriptionmust be one physical YAML-safe line and include trigger words first. - Do not add a
Keywordssection; put essential trigger words indescription. - Put templates, schemas, and generated examples in
assets/. - Put longer rationale or local doc links in
references/. - After changing project skills, refresh the registry with
/skill-registry:refreshwhen available.
Decision Gates
| Need | Action |
|---|---|
| Small reusable behavior | Create skills/{skill-name}/SKILL.md only |
| Templates, schemas, fixtures | Add skills/{skill-name}/assets/ |
| Longer explanation or edge cases | Add skills/{skill-name}/references/ |
| Existing skill covers it | Update the existing skill instead |
| Skill affects delegation discovery | Ensure trigger words appear in description |
Execution Steps
- Read
docs/skill-style-guide.mdbefore creating or updating skills. - Inspect existing skills and confirm the new skill does not duplicate one.
- Choose a kebab-case skill name that matches the user-facing trigger.
- Create or update this structure:
skills/{skill-name}/
├── SKILL.md
├── assets/ # optional
└── references/ # optional
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 · 87 lines · 37 tokens per session scan A 8d13eaf636f5
gentle-ai-skill-creator is a skill published in the GitHub repository Gentleman-Programming/gentle-pi (804 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 728 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
review-team
Use when assigned a review or when an authored review boundary is reached.
pi-parity-review
Adversarially verify that a ported change is faithful to the original pi implementation (TS source + published npm build). Use after porting upstream pi changes, or standalone on any area of this repo ("is X faithful to pi?").
pi-go-review
Review ported Go code for idiomatic quality — that the port maximizes Go rather than transliterating TypeScript. Use after porting upstream pi changes, or standalone on any diff in this repo.
code-review
name: code-review description: Used when the user wants to review code, check quality, verify feature completeness, or needs to validate code implementation against Spec, DESIGN.md, and design mockups. Outputs a structured review report with evidence for each conclusion. version: 2.3.0 updated: 2026-07-16 requires: [].
aih-bugbounty
Scan open PRs and generated ECC/agent artifacts for high-coverage review risks before they are accepted. Use when a PR adds or changes agent bootloaders, Codex or Claude skills, MCP config, generated workflow commands, auto-learning instincts, repository review runbooks, or multi-agent review configuration; also use…
independent-review
Review a batch of changes as an independent reviewer who did not write them, before commit or push. Use after a set of edits, after an autonomous loop, or when the user asks for a pre-commit review.