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 agentmods add skills/hoangatg/ai-agent-toolkit/create-prnpx skills add hoangatg/ai-agent-toolkit --skill create-prgit clone --depth 1 https://github.com/hoangatg/ai-agent-toolkitWrote 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/hoangatg/ai-agent-toolkit/create-pr)<a href="https://agentmods.dev/skills/hoangatg/ai-agent-toolkit/create-pr"><img src="https://agentmods.dev/badge/skills/hoangatg/ai-agent-toolkit/create-pr.svg" alt="Measured on agentmods" 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.00034 | $0.00688 |
| Opus 5 | $0.00017 | $0.00344 |
| Sonnet 5 | $0.00007 | $0.00138 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade A, and why
create-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 2d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create PR
Package your work so reviewers say "yes" quickly.
1. Before Creating PR
Pre-PR Checklist
| Check | Action |
|---|---|
| Tests pass | Run full test suite locally |
| Lint clean | No warnings or errors |
| Self-review | Read your own diff first |
| Small scope | One feature/fix per PR |
| Branch updated | Rebase on latest main |
| No debug code | Remove console.logs, TODO hacks |
2. PR Title
Format
<type>(<scope>): <short description>
Examples
| Good ✅ | Bad ❌ |
|---|---|
feat(auth): add JWT refresh token flow |
update auth |
fix(api): handle null response in user endpoint |
fix bug |
refactor(db): migrate to connection pooling |
changes |
3. PR Description Template
## Summary
One paragraph explaining what this PR does and why.
## Changes
- Added X to handle Y
- Refactored Z for better performance
- Fixed bug where A caused B
## Testing
- [ ] Unit tests added for new logic
- [ ] Manual testing: describe what you tested
- [ ] Edge cases considered: list them
## Screenshots / Recordings
(For UI changes — before/after)
## Related
- Closes #123
- Depends on #456
4. Changelog Entry
Format (Keep a Changelog)
## [Unreleased]
### Added
- JWT refresh token flow for seamless re-authentication
### Fixed
- Null response handling in user API endpoint
### Changed
- Database connection pooling for improved throughput
5. Review-Friendly Practices
| Practice | Why |
|---|---|
| Annotate your PR | Add comments explaining tricky code |
| Stack PRs | Break large features into reviewable parts |
| Highlight risks | Flag areas that need careful review |
| Respond promptly | Don't let review feedback go stale |
| Don't take it personally | Reviews improve code, not judge you |
6. Merge Strategy
| Strategy | When |
|---|---|
| Squash merge | Feature branches → clean history |
| Merge commit | Preserve full branch history |
| Rebase | Linear history, small PRs |
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.
- 2d ago First seen · 125 lines · 34 tokens per session scan A fc469c8262af
create-pr is a skill published in the GitHub repository hoangatg/ai-agent-toolkit (1 stars, last pushed 5mo ago), licensed MIT. It adds 34 tokens to every session and 688 once invoked, about $0.0002 per session on Opus 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-09-03.
Other skills, from other repositories
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
feature
Full per-feature pipeline: implement → testloop → evaluator challenge → coder feedback → document → commit.
quick
/quick — Lightweight Feature Workflow.
opencode
Delegate coding tasks to the OpenCode CLI for feature work, refactoring, PR review, and autonomous-style runs. Requires opencode installed where the agent can execute shell commands.
codex
Delegate coding tasks to the OpenAI Codex CLI for features, refactoring, PR reviews, and batch fixes. Requires the codex CLI and typically a git repository.