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 djscheuf/agentic-dev-ecosystem-template --skill pr-summarygit clone --depth 1 https://github.com/djscheuf/agentic-dev-ecosystem-templateWrote 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/djscheuf/agentic-dev-ecosystem-template/pr-summary)<a href="https://agentmods.dev/skills/djscheuf/agentic-dev-ecosystem-template/pr-summary"><img src="https://agentmods.dev/badge/skills/djscheuf/agentic-dev-ecosystem-template/pr-summary/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/djscheuf/agentic-dev-ecosystem-template/pr-summary"><img src="https://agentmods.dev/badge/skills/djscheuf/agentic-dev-ecosystem-template/pr-summary.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.00011 | $0.01098 |
| Opus 5.5 | $0.00004 | $0.00439 |
| Sonnet 5.5 | $0.00002 | $0.00220 |
| Haiku 4.5 | $0.00001 | $0.00110 |
Grade A, and why
pr-summary 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 1mo 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Summary Workflow
Use this workflow when preparing to merge a feature branch via Pull Request.
Step 1: Gather Branch and Version Information
Check the current branch, version, and commit history:
git branch --show-current
cat package.json | grep '"version"'
git log --oneline --no-merges origin/main..HEAD
Note: Target branch defaults to main unless specified otherwise. Version is automatically read from package.json.
Step 2: Identify Key Components
Review what was implemented by examining:
- API endpoints added/modified
- Business rules enforced
- Test coverage (run tests to get count)
- Infrastructure changes (Docker, database, etc.)
- Documentation created
Step 3: Generate Squash Merge Commit Message
Format: Single-line summary + blank line + body (max 500 characters total)
Template:
<type>: <brief description> (v<version>)
<2-3 sentence overview>
Endpoints: <list endpoints>
Auth: <auth mechanism>
Rules: <key business rules>
Testing: <test count and methodology>
Infrastructure: <key infrastructure components>
Observability: <logging/monitoring features>
Requirements:
- ✅ Max 500 characters (excluding file stats)
- ✅ No file statistics (Git handles this)
- ✅ Focus on WHAT and WHY, not HOW
- ✅ Include version number if applicable
Types: feat, fix, refactor, docs, test, chore, perf, ci
Step 4: Generate PR Description
Format: Markdown with sections
Emoji Selection:
- 📚 Use book emoji for documentation, workflow, or infrastructure changes
- 🎯 Use target emoji for feature implementation with code changes
- 🐛 Use bug emoji for bug fixes
Template:
# <emoji> <Feature Name> (v<version>)
## Overview
<1-2 sentence summary>
## API Endpoints (if applicable)
- `METHOD /path` - Description
## Key Features
- **Category**: Details
- **Category**: Details
## Testing (<count> tests - <status>)
- **Component**: <count> tests (<focus areas>)
## Local Development (if applicable)
```bash
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.
- 1mo ago First seen · 158 lines · 11 tokens per session scan A 3025e39c9273
pr-summary is a skill published in the GitHub repository djscheuf/agentic-dev-ecosystem-template (12 stars, last pushed 20d ago), licensed MIT. It adds 11 tokens to every session and 1,098 once invoked, about $0.0000 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-09-13.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.