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/petermefrandsen/rtk-inspector/create-prnpx skills add petermefrandsen/rtk-inspector --skill create-prgit clone --depth 1 https://github.com/petermefrandsen/rtk-inspectorWrote 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/petermefrandsen/rtk-inspector/create-pr)<a href="https://agentmods.dev/skills/petermefrandsen/rtk-inspector/create-pr"><img src="https://agentmods.dev/badge/skills/petermefrandsen/rtk-inspector/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.00044 | $0.02058 |
| Opus 5 | $0.00022 | $0.01029 |
| Sonnet 5 | $0.00009 | $0.00412 |
| Haiku 4.5 | $0.00004 | $0.00206 |
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 5d 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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
create-pr
Mission
Create a GitHub pull request for the current branch with a valid Conventional Commits title and an auto-generated description that summarizes the actual changes.
Prerequisites
gitandghCLI installed and authenticated (gh auth status).- The
ghtoken must include theprojectscope for project assignment. If missing, run:gh auth refresh -s project - The current branch is not
main. - Changes have been committed and pushed to the remote.
PR title rules
The title must pass the repository PR title checker. The authoritative pattern is defined in
.github/pr-title-checker-config.json — read that file at runtime to get the current CHECKS.regexp
value rather than relying on a hardcoded pattern.
Additional prose rules (not fully enforced by the checker):
- The
!breaking-change indicator must appear after the optional scope and before the:, never between the type and the scope (for examplefeat!(scope):is invalid;feat(scope)!:is correct). - The
:must be followed by a single space and a non-empty description.
Allowed types: feat, fix, docs, test, ci, chore, refactor.
Format:
<type>[optional scope][!]: <description>
Examples:
feat(cmdb): add bulk object creation endpointfix(auth): handle expired JWT gracefullydocs: update README with new env varsrefactor(services)!: replace requests with httpx
PR description template
The body must use the structure from .github/pull_request_template.md:
# Pull request description
## Describe your changes
<auto-generated summary — see below>
## Issue ticket number and link
<leave blank or fill if the user provides one>
## Checklist before requesting a review
- [ ] I have performed a self-review of my code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] Any dependent changes have been merged and published in downstream modules
- [ ] New or updated tests follow the AAA pattern and `test_<feature>_should_<expected behavior>_when_<state under test>` naming convention
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.
- 5d ago First seen · 203 lines · 44 tokens per session scan A b943e5371389
create-pr is a skill published in the GitHub repository petermefrandsen/rtk-inspector (1 stars, last pushed 3mo ago), licensed MIT. It adds 44 tokens to every session and 2,058 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-08-31.
Other skills, from other repositories
impact-audit
Blast radius of a change you have not made yet -- traces a symbol across federated repositories, splits impact per repo, and reports what must ship together.
onboard-repo
Index an unfamiliar codebase into the knowledge graph, then produce a first orientation map -- entry points, most-depended-upon modules, hotspots, test topology.
security-sweep
Graph-driven security sweep -- scan for dangerous sinks, then rank each finding by whether an entry point can actually reach it, and triage the rest into suppressions.
refactor-check
Safety analysis before refactoring -- dependency graph, test coverage, public API exposure, blast radius verdict.
review-pr
Review a PR or branch diff using the knowledge graph for full structural context. Outputs a structured review with blast-radius analysis.
build-graph
Build or update the code review knowledge graph. Run this first to initialize, or let hooks keep it updated automatically.