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 artivilla/agents-config --skill pr-trendsgit clone --depth 1 https://github.com/artivilla/agents-configWrote 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/artivilla/agents-config/pr-trends)<a href="https://agentmods.dev/skills/artivilla/agents-config/pr-trends"><img src="https://agentmods.dev/badge/skills/artivilla/agents-config/pr-trends/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/artivilla/agents-config/pr-trends"><img src="https://agentmods.dev/badge/skills/artivilla/agents-config/pr-trends.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.00072 | $0.00482 |
| Opus 5 | $0.00036 | $0.00241 |
| Sonnet 5 | $0.00014 | $0.00096 |
| Haiku 4.5 | $0.00007 | $0.00048 |
Grade A, and why
pr-trends 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 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.
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.
What it actually says
PR Trends
Use this skill when the user wants a repo-level pull request trend report.
Quick start
Run the bundled script from the target repository:
node .agents/skills/pr-trends/scripts/report-pr-trends.mjs
Useful options:
node .agents/skills/pr-trends/scripts/report-pr-trends.mjs --repo /path/to/repo
node .agents/skills/pr-trends/scripts/report-pr-trends.mjs --mode gh
node .agents/skills/pr-trends/scripts/report-pr-trends.mjs --mode git
Source selection
--mode auto: trygh pr listfirst for exact PRcreatedAt,mergedAt, and line counts. Fall back togitifghis unavailable or offline.--mode gh: require GitHub CLI data. Use this when the user needs exact PR creation trends and accurate days-to-merge.--mode git: use only local mainline history. This gives reliable merged counts and merged lines changed, but it cannot recover exact PR creation timestamps or closed-unmerged PRs.
Output
The script prints:
- A weekly summary table
- A monthly summary table
- A short note describing which data source was used
Interpretation
Createdis grouped by PR creation time when GitHub metadata is available.Merged,Avg Days, andLines Δare grouped by merge time.- In
gitfallback mode,CreatedandAvg Daysare shown as-because local git history does not preserve complete PR lifecycle metadata.
Notes
- Run from the repo root unless
--repois provided. - The script reads first-parent history so the report reflects the mainline branch.
- If the fallback note mentions missing PR numbers, treat those as likely closed, unmerged, or otherwise not reconstructable from local git alone.
What ships with it
2 files 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.
- 9d ago First seen · 51 lines · 72 tokens per session scan A 10e07236cfaf
pr-trends is a skill published in the GitHub repository artivilla/agents-config (0 stars, last pushed 3mo ago), licensed MIT. It adds 72 tokens to every session and 482 once invoked, about $0.0004 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
skill-upstream-pr
Improve an open-source GitHub skill and open a friendly suggestion PR upstream: fork, run skill-auto-improver, attach asm eval before/after metrics. Don't use for local-only skills, authoring from scratch, bulk repos, or registry publish.
meanest-editor
Roast a pitch or press release with the eye of a veteran PR director. Honest, sharp, constructive — never cruel for its own sake.
headline-generator
Generate headline candidates from a story's raw facts: news-style headlines, press-release headlines, and pitch subject lines. A pure generation skill — it finds the charge in the facts, then runs ten proven moves (consequence, picture, number-as-hero, two-beat turn, naming, reader's-own-story, open question, voice…
ai-visibility-writing
Audit, question, suggest, or fact-preservingly revise a press release, blog post, contributed article, or expert explainer so AI answer systems can more easily retrieve, understand, quote, and cite its useful information. Use when someone asks for AI visibility, AI search, answer-engine, AEO, GEO, AI Overview, or…
docs-updater
Provides automated documentation updates by analyzing git changes between the current branch and the last release tag. Performs git diff analysis to identify modifications, then updates README.md, CHANGELOG.md following Keep a Changelog standard, and discovers documentation folders for contextual updates. Use when…
github-issue-workflow
Provides a structured 8-phase workflow for resolving GitHub issues in Claude Code. Covers fetching issue details, analyzing requirements, implementing solutions, verifying correctness, performing code review, committing changes, and creating pull requests. Use when user asks to resolve, implement, work on, fix, or…