Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add bdfinst/agentic-dev-team/plugin install dev-teamWrote 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/bdfinst/agentic-dev-team/pr)<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/pr"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/pr/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/bdfinst/agentic-dev-team/pr"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/pr.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.00059 | $0.03607 |
| Opus 5.5 | $0.00024 | $0.01443 |
| Sonnet 5.5 | $0.00012 | $0.00721 |
| Haiku 4.5 | $0.00006 | $0.00361 |
Grade A, and why
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 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 — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Request
Role: orchestrator. This command enforces quality gates before creating a PR.
You have been invoked with the /pr command.
Orchestrator constraints
- Run the quality gate and open the PR; do not bypass failing gates.
- Delegate review to the review agents; do not review code yourself.
- Be concise. Report gate results and the PR URL, no preamble.
Parse Arguments
Arguments: $ARGUMENTS
--skip-review: Skip the/code-reviewstep (not recommended)--draft: Create a draft PR--base <branch>: Target branch (default:main)--no-auto-merge: Do not enable auto-merge (the default is to enable it; see Step 5)
Steps
1. Pre-flight checks
Verify:
- Current branch is not
mainormaster - There are commits ahead of the base branch
- Working tree is clean (no uncommitted changes) — if dirty, ask whether to commit or stash
If a plan file is present (check plans/ for the most recently modified approved or implemented plan), run the plan completion gate:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/progress_guardian.py" --pre-pr --plan <plan-file>
A non-zero exit means incomplete steps remain; stop and surface the findings — do not open the PR until all steps are [x].
2. Run quality gate
Run each check sequentially. Stop on first failure:
-
Tests: Detect and run the project's test suite
package.jsonscripts:npm testorpnpm testoryarn testpytest.ini/pyproject.toml:pytestgo.mod:go test ./...Cargo.toml:cargo test*.csproj:dotnet testMakefilewithtesttarget:make test
-
Type check (if applicable):
tsconfig.json:npx tsc --noEmitmypy.ini/ pyproject.toml with mypy:mypy .
-
Lint (if applicable):
eslintin deps:npx eslint .ruffavailable:ruff check .golangci-lintavailable:golangci-lint run
-
Code review (unless
--skip-review):- Scope the review to this branch's diff against the base branch, not the whole repo. At PR time the working tree is clean (Step 1 requires it), so a bare
/code-review --jsonwould auto-scope to the full repository — expensive, wrongly scoped, and on a large repo it can trigger the sliced-review path. Compute the merge base:
- Scope the review to this branch's diff against the base branch, not the whole repo. At PR time the working tree is clean (Step 1 requires it), so a bare
What ships with it
1 file 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.
- 1mo ago First seen · 279 lines · 59 tokens per session scan A 607d2eb7b7e0
pr is a skill published in the GitHub repository bdfinst/agentic-dev-team (295 stars, last pushed 4d ago), licensed MIT. It adds 59 tokens to every session and 3,607 once invoked, about $0.0002 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-03.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
git-pr-workflows-git-workflow
Guide changes through code checks, testing, commits, and pull request preparation. Use when coordinating a complete Git workflow and verifying readiness for collaboration.