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 tellmefrankie/news-engine --skill pr-review-prepgit clone --depth 1 https://github.com/tellmefrankie/news-engineWrote 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/tellmefrankie/news-engine/pr-review-prep)<a href="https://agentmods.dev/skills/tellmefrankie/news-engine/pr-review-prep"><img src="https://agentmods.dev/badge/skills/tellmefrankie/news-engine/pr-review-prep/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/tellmefrankie/news-engine/pr-review-prep"><img src="https://agentmods.dev/badge/skills/tellmefrankie/news-engine/pr-review-prep.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.00000 | $0.00792 |
| Opus 5 | $0.00000 | $0.00396 |
| Sonnet 5 | $0.00000 | $0.00158 |
| Haiku 4.5 | $0.00000 | $0.00079 |
Grade A, and why
pr-review-prep 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 11d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Review Prep
Generate a complete pull request description from your git diff. Includes summary, test plan, risk assessment, and reviewer notes — in under 10 seconds.
What it does
- Reads
git diff main...HEAD(or any branch pair) - Classifies changes: new feature, bug fix, refactor, dependency update, config change
- Writes PR title (under 70 chars), summary bullets, test plan checklist
- Flags risk areas: database migrations, auth changes, public API surface changes
- Identifies files that need extra reviewer attention
- Optionally creates the PR via
gh pr create
Usage
Prepare my PR description.
Branch: feat/options-flow-lottery-filter vs main
Include: summary, what changed, test plan, risk level, files to review carefully.
Format for GitHub PR body (markdown).
Example Output
## Summary
- Add real/lottery call separation to options flow analyzer
- Lottery threshold: premium < $0.10 OR delta < 0.05
- Adjusted P/C ratio now excludes lottery volume before sentiment classification
- Anomaly detection baseline unchanged; now runs on adjusted ratio
## What changed
**Core logic** (`src/options/analyzer.ts`)
- `splitRealVsLottery()` — new function, filters options by premium + delta thresholds
- `computeAdjustedPC()` — replaces raw P/C with filtered ratio
- Sentiment thresholds unchanged (< 0.45 = bullish, > 1.5 = bearish)
**Types** (`src/types/index.ts`)
- Added `LotteryMetrics` type: `{ lotteryPct, realCallOI, realPutOI }`
**Tests** (`tests/options.test.ts`)
- 4 new test cases: RXRX 84% lottery inversion, KTOS clean signal, edge cases
## Test Plan
- [ ] Run `pnpm test` — all existing tests pass
- [ ] Manual: run analyzer on RXRX — confirm adj P/C ≠ raw P/C when lottery > 50%
- [ ] Manual: run on KTOS — confirm adj P/C close to raw when lottery < 30%
- [ ] Check Polygon API error handling still works (mock API key test)
## Risk Assessment
Risk level: LOW
- No DB schema changes
- No public API surface changes
- Additive only — raw P/C still computed, adj P/C is additional field
- Backward compatible with existing callers
## Files needing careful review
- `src/options/analyzer.ts` — core logic change, review threshold values
- `src/types/index.ts` — new type, ensure downstream consumers updated
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.
- 11d ago First seen · 101 lines · 0 tokens per session scan A 15815744b878
pr-review-prep is a skill published in the GitHub repository tellmefrankie/news-engine (1 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 792 tokens. 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
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
github
GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available)…
issue-to-pr-resolver
Implement a GitHub issue end-to-end — create a worktree branch, implement the feature with tests, create a draft PR, then iteratively resolve all CI failures and review comments until the PR is clean. Use when you need to fully implement a GitHub issue from start to merge-ready. Triggers on "implement issue", "resolve…
my-pr-checker
Manage your own GitHub pull requests — check CI status, inline review comments, PR-level comments, resolve review threads, fix issues, and iterate until all checks pass and threads are resolved. Use for managing your own PRs (not external contributions). Triggers on "check my PR", "check PR", "/my-pr-checker ".
meta-codereview-current-diff
Read the current uncommitted diff, run three independent reviewers (safety + tests-coverage + style) in parallel, then arbitrate a single BLOCK / BLOCKWITHOVERRIDE / PASSWITHNOTES verdict. Use before commit when you want a multi-perspective second-opinion instead of a single-reviewer agent loop.
goal-pr
Drive a pull request to a clean state and merge it: run the review-pr skill, fix every mid-or-above finding, and repeat until no mid-or-above findings remain, then merge. Use when the user wants to finish a PR by reviewing, fixing, and merging it, or triggers on "the goal-pr skill".