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 jellydn/my-ai-tools --skill prgit clone --depth 1 https://github.com/jellydn/my-ai-toolsWrote 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/jellydn/my-ai-tools/pr)<a href="https://agentmods.dev/skills/jellydn/my-ai-tools/pr"><img src="https://agentmods.dev/badge/skills/jellydn/my-ai-tools/pr/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/jellydn/my-ai-tools/pr"><img src="https://agentmods.dev/badge/skills/jellydn/my-ai-tools/pr.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.00025 | $0.01245 |
| Opus 5.5 | $0.00010 | $0.00498 |
| Sonnet 5.5 | $0.00005 | $0.00249 |
| Haiku 4.5 | $0.00003 | $0.00125 |
Grade A, and why
pr 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 10d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reviewable Pull Request
Prepare a pull request body that lets a human understand the change quickly, verify that it works, and spend review time where risk is highest. This skill improves the review narrative; it does not replace code review or validation.
When to Use
Use when:
- A branch has a meaningful diff and needs a new or updated PR body.
- The reviewer needs the shape of a refactor, flow, or integration explained.
- The change has evidence and rollback implications worth making explicit.
Load draft-pull-request for repository preflight, branch handling, and gh publication rules. Reuse an existing PR instead of opening a duplicate.
Required Inputs
Before writing, gather:
- The authoritative spec, issue, plan, or ticket graph.
- The complete diff against the PR base.
- The actual commands run and their output.
- Any screenshots, logs, or before/after behavior available.
- If a skill or workflow changed, the original input plus the pre-edit and post-edit outputs.
- The current PR template and existing reviewer notes.
Never claim a test, screenshot, or manual check that was not actually run.
Body Template
Use these sections unless the repository's template requires equivalent headings:
## Summary
<the smallest visual that explains the change>
## Evidence
- **Before:** <failing test, old output, old screenshot, or baseline behavior>
- **After:** <passing test, new output, new screenshot, or verified behavior>
## Merge Danger
**Door:** <two-way or one-way>
**Blast Radius:** <one-word scope>
<what can break, what rollback restores, and where careful review matters>
Summary: show the shape
Choose one small visual, not a prose dump:
- Call tree for runtime control flow.
- Component tree for UI changes.
- File tree for ownership or layout changes.
- Diff sketch for a focused behavior change.
- Mermaid sequence or flow for cross-component data movement.
- Pseudocode for an algorithm or state transition.
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.
- 10d ago First seen · 151 lines · 25 tokens per session scan A d173b3d1a61b
pr is a skill published in the GitHub repository jellydn/my-ai-tools (123 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 1,245 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-10-07.
Other skills, from other repositories
check
Reviews diffs, PRs, release readiness, and publishing follow-through. Use when asked to review, triage issues or PRs, or ship. Not for debugging root causes or prose.
antfu-create-pr
Create a reviewable GitHub pull request from the current branch with a Conventional Commits title, a concise evidence-based body, and before/after screenshots for UI changes. Use when asked to open, create, publish, or prepare a PR.
factory-babysit-pr
Experimental workflow for babysitting one explicitly authorized pull or merge request. Use to monitor its live review state and checks, fix actionable in-scope findings, and apply separate reply, approval, merge, and soak gates.
factory-review-prs
Experimental workflow for reviewing configured repositories' pull requests. Use for manual or scheduled PR triage, approval, or merge decisions.
comet-github-pr-review
A read-only review process for pull requests in Comet's GitHub repositories. A pull request is a proposed code change; the review checks its current code, related issue, comments, merge status, and automated checks.
pr-description-writer
Redacta una descripción de pull request clara y estructurada a partir de un diff de git, resumen de rama o lista de commits. Úsalo cuando te pidan escribir una descripción de PR, redactar una solicitud de cambios o documentar cambios de código. Produce una descripción con resumen, motivación, cambios realizados, pasos…