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 agentmods add rules/adonai-labs/agent-runway/pull-request-templatesgit clone --depth 1 https://github.com/adonai-labs/agent-runwayWrote 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/rules/adonai-labs/agent-runway/pull-request-templates)<a href="https://agentmods.dev/rules/adonai-labs/agent-runway/pull-request-templates"><img src="https://agentmods.dev/badge/rules/adonai-labs/agent-runway/pull-request-templates.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00982 |
| Opus 5 | $0.00000 | $0.00491 |
| Sonnet 5 | $0.00000 | $0.00196 |
| Haiku 4.5 | $0.00000 | $0.00098 |
Grade A, and why
pull-request-templates 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 4d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Request Templates and Team Standards
Standard PR Template
### Type of Change
- [ ] Bug fix (non-breaking)
- [ ] New feature (non-breaking)
- [ ] Breaking change
- [ ] Documentation | Performance | Refactoring | Test | CI/CD
### Description
Brief description of changes.
### Related Issues
Closes #123 | Fixes #456 | Related to #789
### Testing
- [ ] Unit | Integration | E2E tests pass
- [ ] Manual testing completed
### Checklist
- [ ] Code follows style guidelines | Self-review done
- [ ] No console.log/TODO in production code
- [ ] Error handling | Security | Performance considered
Feature PR Template
### Feature Description
Brief description of the feature.
### Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2
### Technical Summary
Architecture, DB/API/Frontend changes, security considerations.
### Breaking Changes
- [ ] None | Document below
### Rollback Plan
How to rollback if issues arise.
Bug Fix PR Template
### Bug Description
What the bug was and its impact.
### Root Cause
What caused it and why.
### Fix
How the bug was fixed.
### Verification Steps
1. Step 1
2. Step 2
### Regression Testing
- [ ] Existing functionality intact
- [ ] No new bugs | Performance | Security unchanged
Hotfix PR Template
### Issue
Critical issue requiring immediate fix.
### Severity
Critical | High | Medium | Low — affected users, business impact.
### Fix
Quick description of the fix.
### Deployment Plan
- [ ] Ready for immediate deployment
- [ ] Rollback plan prepared | Monitoring configured
### Post-Deployment
- [ ] Monitor 24h | Verify in production | Schedule follow-up
Commit Conventions
Format: <type>[optional scope]: <description>
| Type | Use |
|---|---|
| feat | New feature |
| fix | Bug fix |
| docs | Documentation only |
| style | Formatting, no logic change |
| refactor | Code change, no bug fix or feature |
| perf | Performance improvement |
| test | Add or fix tests |
| chore | Build, tooling, deps |
| ci | CI config |
| build | Build system |
| revert | Revert previous commit |
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.
- 4d ago First seen · 172 lines · 0 tokens per session scan A e81b2caf15ea
pull-request-templates is a cursor rule published in the GitHub repository adonai-labs/agent-runway (2 stars, last pushed 14d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 982 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 cursor rules, from other repositories
archgate-governance
Archgate ADR governance — enforces architecture decision records.
cursorrules
When the user asks you to generate diagrams, analyze code structure, or visualize architecture, follow this analysis pipeline. Use terminal commands (rg, find, cat) for all file operations.
arch4
Keep Arch4 architecture maps current.
cursorrules
You are working with a React Native (Expo) architecture reference project. Read the skill files before generating any code.
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
frontend-architecture
Vite + React SPA architecture - directory layout, providers, bundle splitting. Tailwind styling in tailwind.mdc.