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 this-is-tobi/tools --skill pull-requestgit clone --depth 1 https://github.com/this-is-tobi/toolsWrote 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/this-is-tobi/tools/pull-request)<a href="https://agentmods.dev/skills/this-is-tobi/tools/pull-request"><img src="https://agentmods.dev/badge/skills/this-is-tobi/tools/pull-request/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/this-is-tobi/tools/pull-request"><img src="https://agentmods.dev/badge/skills/this-is-tobi/tools/pull-request.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.00030 | $0.00625 |
| Opus 5.5 | $0.00012 | $0.00250 |
| Sonnet 5.5 | $0.00006 | $0.00125 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
pull-request 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 19d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Request Description
Generate clear, comprehensive PR descriptions that help reviewers understand and evaluate changes.
Do not mention the AI assistant in the PR description (eg., "This PR was generated by an AI assistant"). Instead, focus on the changes made, their purpose, and any relevant context.
Priority: Check for Templates First
Before generating a custom description, check for existing PR templates:
.github/PULL_REQUEST_TEMPLATE.md.github/pull_request_template.md.github/PULL_REQUEST_TEMPLATE/(directory)PULL_REQUEST_TEMPLATE.md(root)
If templates exist, use them. Otherwise, check for organization-level templates in the .github repository. And if there are no templates, generate a custom description using the structure below.
Structure
## Summary
[One-line description of the change]
## Purpose & Context
**Problem:** [What issue are we solving?]
**Solution:** [How does this PR address it?]
**Related Issues:** Fixes #123, Relates to #456
## Changes Made
**[Module/Component]:**
- Change 1
- Change 2
**Tests:**
- Unit tests added/updated
- Integration tests for critical paths
## Testing
**Automated:** ✅ Unit (X tests) · ✅ Integration (Y scenarios)
**Manual:** ✅ Tested on [browsers/devices/environments]
**Coverage:** X% → Y%
## Screenshots/Demo (if applicable)
[Before/after screenshots or GIFs for UI changes]
## Breaking Changes (if any)
⚠️ [What changed, who is affected, migration path]
## Additional Notes
[Performance, security, known limitations, deployment considerations]
## Checklist
- [ ] Tests added/updated
- [ ] Documentation updated
- [ ] No breaking changes (or documented)
- [ ] Self-reviewed the code
- [ ] Ready for review
Section Guidelines
Summary: One line, max 100 chars, imperative mood, focus on the most important change.
Purpose & Context: Explain "why", link issues/tickets, include business context.
Changes Made: Organize by component, use bullet hierarchy, include both code and test changes.
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.
- 19d ago Changed · -1 lines 0b896f0e022f
- 2mo ago First seen · 95 lines · 30 tokens per session scan A 0140194e471c
pull-request is a skill published in the GitHub repository this-is-tobi/tools (5 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 625 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-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…