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 softspark/ai-toolkit --skill prgit clone --depth 1 https://github.com/softspark/ai-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/softspark/ai-toolkit/pr)<a href="https://agentmods.dev/skills/softspark/ai-toolkit/pr"><img src="https://agentmods.dev/badge/skills/softspark/ai-toolkit/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/softspark/ai-toolkit/pr"><img src="https://agentmods.dev/badge/skills/softspark/ai-toolkit/pr.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.00036 | $0.01323 |
| Opus 5.5 | $0.00014 | $0.00529 |
| Sonnet 5.5 | $0.00007 | $0.00265 |
| Haiku 4.5 | $0.00004 | $0.00132 |
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 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Request
$ARGUMENTS
Create or update the task's GitHub pull request after project-specific checks.
When called by /autonomous-dev, preserve its run ID, branch, PR identity,
approval history and evidence. This skill publishes the PR; the calling process
owns subsequent review, QA and required-CI completion.
Project context
- Inspect the actual repository, branch and working tree. Resolve the base from
an existing PR first, then project configuration or the remote default branch.
Do not assume a branch named
mainexists.
Usage
/pr [title]
Automated PR Summary Generation
Generate a structured PR summary from the commit history before writing the PR description:
python3 ${CLAUDE_SKILL_DIR}/scripts/pr-summary.py [base_branch]
# Pass the resolved PR base explicitly, for example develop.
The script outputs JSON with:
- title_suggestion: auto-generated PR title from dominant commit type and scope
- commits[]: each commit parsed into type, scope, description (conventional commits)
- groups: commits grouped by type (Features, Bug Fixes, etc.)
- summary_bullets: ready-to-use summary lines for the PR body
- has_breaking: whether any BREAKING CHANGE markers were found
- breaking_changes[]: list of breaking change descriptions
- files_changed: total files in the diff
- test_files_changed: count of test files modified
- has_tests: whether the PR includes test changes
Use the output to populate the PR template fields below.
PR Creation Workflow
1. Pre-PR Checks
Read the project's instructions, CI configuration and package/Make scripts.
For an autonomous run, use the commands frozen in its plan from
.ai-toolkit/autonomous.json. Run the actual lint, typecheck, test and build
commands applicable to that project; a Python command is not a universal gate.
Inspect every result and preserve evidence of the tested commit. Missing runtime
services or failed commands are blockers, never successful checks.
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.
- 1mo ago Changed · +5 lines 2dcf09817729
- 1mo ago First seen · 153 lines · 36 tokens per session scan A b5017357f97a
pr is a skill published in the GitHub repository softspark/ai-toolkit (180 stars, last pushed 5d ago), licensed Apache-2.0. It adds 36 tokens to every session and 1,323 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-09-03.
Other skills, from other repositories
git-commit
Safely create a git commit by validating repository state, staging intended changes, scanning for secrets/conflicts, generating a Conventional Commits message (repository convention first, else an English Angular default) from the staged diff, and committing without amend.
git-workflow-helper
Guide pour les opérations Git complexes, résolution de conflits et bonnes pratiques de workflow. À utiliser quand l'utilisateur est bloqué avec Git ou veut mettre en place un workflow. Se déclenche aussi avec "git merge conflict", "comment revert", "git rebase", "branching strategy", "j'ai cassé mon git", ou toute…
github-readme
Generate, audit, or update GitHub READMEs with project-type-aware structure, voice calibration, and SEO/AEO discoverability guidance. Three modes: generate (new), audit (check existing), update (patch). Detects repo type and adapts sections, tone, and badges accordingly.
safe-push
Pre-push hygiene check for GitHub repositories. Scans for PII, secrets, and sensitive data before pushing. Audits commit messages, enforces repo-specific blocklists, and rate-limits pushes to avoid GitHub abuse detection. Use before any git push, especially to public repos.
git-workflow
Git workflow automation with conventional commits, merge vs rebase decision trees, worktrees, SSH signing, and monorepo sparse checkout patterns.
git-conventions
Apply when committing, branching, or opening a pull request. Conventional commit format, branch naming, PR scope.