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 nortonx/ai-tooling-free --skill pr-descriptiongit clone --depth 1 https://github.com/nortonx/ai-tooling-freeWrote 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/nortonx/ai-tooling-free/pr-description)<a href="https://agentmods.dev/skills/nortonx/ai-tooling-free/pr-description"><img src="https://agentmods.dev/badge/skills/nortonx/ai-tooling-free/pr-description/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/nortonx/ai-tooling-free/pr-description"><img src="https://agentmods.dev/badge/skills/nortonx/ai-tooling-free/pr-description.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.00019 | $0.00812 |
| Opus 5 | $0.00010 | $0.00406 |
| Sonnet 5 | $0.00004 | $0.00162 |
| Haiku 4.5 | $0.00002 | $0.00081 |
Grade A, and why
pr-description scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| API route file (e.g., `routes/`, `controllers/`, `*Controller.*`, `app.py` Flask routes) | "Hit the endpoint with curl/Postman: `curl <method> <url>` — expect `<status>` and `<body shape>`." | How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arguments
[<base-branch>]
- Optional. The branch to diff against; defaults to
main. - Examples:
/pr-description,/pr-description develop
Copilot CLI note:
$ARGUMENTSdoesn't substitute in skills — include the argument inline in your prompt.
Generate a pull request description for the current branch.
Base branch from $ARGUMENTS (default: "main").
Steps:
- Get branch name:
git branch --show-current - Get commit list:
git log <base-branch>..HEAD --pretty=format:"- %s" --no-merges - Get changed files:
git diff <base-branch>..HEAD --name-status - Get diff summary:
git diff <base-branch>..HEAD --stat
Format output as:
Summary
<1-2 sentence description of what this PR does and why>
Changes
<bullet list from commits, grouped by area if possible>
Files Changed
<list from diff --name-status, grouped by type: Added / Modified / Deleted>
How to test
- <step 1>
- <step 2>
Notes
<any breaking changes, dependencies, or deploy considerations>
Infer testing steps using this routing table — first match wins, list the matching steps in ## How to test:
| Changed file shape | Test step to include |
|---|---|
*.test.* / *.spec.* / tests/** only |
"Run <project test command> — added/updated tests cover the change." |
API route file (e.g., routes/, controllers/, *Controller.*, app.py Flask routes) |
"Hit the endpoint with curl/Postman: curl <method> <url> — expect <status> and <body shape>." |
| Database migration | "Run the migration on a dev DB, then run the reverse, then re-run forward. Confirm schema matches <file>." |
UI component (.vue, .tsx, .jsx) |
"Open the affected view in the running app (<dev command>), exercise the changed interaction, confirm <expected visible result>." |
| Config / build / CI file | "Re-run the affected pipeline locally (e.g., npm run build, ./scripts/check.sh) — confirm no new warnings or failures." |
Docs-only (.md, .rst, docs/**) |
"Read for clarity; no functional test needed." |
| Mix of the above | List one step per category, in the order above. |
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 · 72 lines · 19 tokens per session scan A 398429ff5892
pr-description is a skill published in the GitHub repository nortonx/ai-tooling-free (1 stars, last pushed 25d ago), licensed MIT. It adds 19 tokens to every session and 812 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
lov-gh-access
Open a private GitHub repo to external clients or contractors without making it public. Accepts a mixed list of GitHub usernames and/or email addresses, resolves each to a GitHub account (falling back to an email invitation when the user has no discoverable account yet), and invites them as collaborators with a chosen…
lov-gh-tidy
Interactive GitHub repo hygiene skill. Lists all open issues, PRs, stale branches, and orphan labels, shows a summary of each with analysis, then asks the user how to handle each item (close, merge, comment, delete, keep). Executes all chosen actions via gh CLI. Use when the user says "清理 GitHub", "tidy repo", "clean…
intuitive-squash
Squash local GSD or agent-generated commit history into a clean, reviewable story while preserving important fixes. Use when the user asks to squash commits, clean git history, compress phase commits, prepare a branch before PR, compare aggressive vs moderate squash options, or preserve hotfix/security commits during…
create-pr
Create evidence-backed pull requests to the GitHub main branch with strict preflight, quality, and security gates. Use when users ask to create/submit/open/update a PR to main (including private repos), decide draft vs ready state, and provide reviewer-ready context for team review.
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.
using-git-worktrees
Use when you need multiple branches checked out at once — create isolated working directories for parallel development without cloning the repository repeatedly.