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 davidmigloz/ai_clients_dart --skill create-prgit clone --depth 1 https://github.com/davidmigloz/ai_clients_dartWrote 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/davidmigloz/ai_clients_dart/create-pr)<a href="https://agentmods.dev/skills/davidmigloz/ai_clients_dart/create-pr"><img src="https://agentmods.dev/badge/skills/davidmigloz/ai_clients_dart/create-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/davidmigloz/ai_clients_dart/create-pr"><img src="https://agentmods.dev/badge/skills/davidmigloz/ai_clients_dart/create-pr.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 Excessive Agency · line 301 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00080 | $0.03640 |
| Opus 5 | $0.00040 | $0.01820 |
| Sonnet 5 | $0.00016 | $0.00728 |
| Haiku 4.5 | $0.00008 | $0.00364 |
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 9d 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 — 349 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create PR Skill for ai_clients_dart
This skill creates pull requests with proper conventional commit titles, structured descriptions that serve as extended changelog entries, correct labels, and the right assignees. It analyzes changes, creates commits, generates a branch, and opens the PR via gh.
Parse $ARGUMENTS for options:
--draft— create the PR as a draft--base <branch>— target a different base branch (default:main)- Any remaining free-form text is treated as context or instructions about which changes to include or how to describe them
Step 1: Validate Environment
- CLI availability:
gitandghmust be on PATH. - GitHub auth:
gh auth statusmust show authenticated. - Repository root: Use
git rev-parse --show-toplevelto determine the repo root. All commands should use absolute paths orcdto repo root first (Bash doesn't persistcdbetween calls). - Base branch: Resolve
{base}from--baseargument (default:main). Verify it exists:git rev-parse --verify {base}. If it fails, trygit fetch origin {base}and re-verify. If still invalid, report the error and stop.
Step 2: Analyze Changes
Gather the full picture of what needs to go into the PR.
-
Uncommitted changes:
git status --porcelain # all modified/untracked/staged files git diff --stat # unstaged changes summary git diff --cached --stat # staged changes summary -
Existing commits on branch (if already on a non-base branch):
git log {base}..HEAD --oneline # {base} is the --base argument, default: main -
Categorize by package: For each changed file, extract the
packages/{pkg}/prefix. Files outsidepackages/go into a "root" category. -
No changes? If the working tree is clean AND there are no commits ahead of the base branch, report this and stop.
-
User-specified subset: If the user's instructions mention specific files or packages to include, filter to only those. Otherwise, include all changes by default — the user asked for a PR, so include everything. Only ask for clarification if the user's
$ARGUMENTSmention a package or scope but it's genuinely ambiguous which files they mean.
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.
- 9d ago First seen · 349 lines · 80 tokens per session scan A 42d0c9fe949d
create-pr is a skill published in the GitHub repository davidmigloz/ai_clients_dart (24 stars, last pushed yesterday), licensed MIT. It adds 80 tokens to every session and 3,640 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.