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.
git clone --depth 1 https://github.com/AdobeDocs/ff-services-docsWrote 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/adobedocs/ff-services-docs/pr-rules)<a href="https://agentmods.dev/rules/adobedocs/ff-services-docs/pr-rules"><img src="https://agentmods.dev/badge/rules/adobedocs/ff-services-docs/pr-rules/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/rules/adobedocs/ff-services-docs/pr-rules"><img src="https://agentmods.dev/badge/rules/adobedocs/ff-services-docs/pr-rules.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.01041 | $0.01041 |
| Opus 5.5 | $0.00416 | $0.00416 |
| Sonnet 5.5 | $0.00208 | $0.00208 |
| Haiku 4.5 | $0.00104 | $0.00104 |
Grade A, and why
pr-rules 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull requests (PRs)
When you draft or review a pull request title or description (for example in GitHub/GitLab or when asked in Agent chat), follow these conventions.
Deriving the Jira issue
- Source of truth: Derive the Jira issue ID from the current Git branch name (for example a segment matching your project key pattern, such as
FFENT-8796). - If the branch name includes a Jira ID: Use that ID in the PR title (see below) and link it in
# Context→## Jira. - If the branch name does not include a Jira ID: Treat the PR as not associated with a ticket. Omit the Jira key from the PR title (do not invent a ticket). Still include
# Context→## Jira, with the content exactly:No ticket(no link).
PR title
When the branch name includes a Jira issue ID, include both:
- The Jira issue ID (e.g.
FFENT-8001). - The commit type (see list below), using this pattern:
{type}/{JIRA-ID}- {short task description}
Example:
feat/FFENT-8001- Add validation for numVariations in OCAPI request
Use a concise imperative-style description after the ID. Match the spacing pattern shown: type, slash, Jira key with trailing hyphen, space, then the description.
When the branch name does not include a Jira issue ID, omit the ticket from the title and use:
{type}- {short task description}
Example:
docs- Refresh Object Composite API changelog
Acceptable commit types (use exactly these labels before /)
- feat — adds a new feature. When a new TOC item is added or the JIRA is connected to another
feat- labeled Jira. - fix — fixes a bug
- refactor — rewrites/restructures code without changing behavior
- perf — improves code performance (special refactor)
- style — formatting/whitespace changes or refactoring the content architecture; no meaning change. Only edits
- test — adds or corrects tests
- docs — new content added; documentation only
- build — build tools, CI, dependencies, project version, etc.
- ops — infrastructure, deployment, backup, recovery, etc.
- chore — miscellaneous (e.g.
.gitignore)
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 · 140 lines · 1,041 tokens per session scan A 413bb5fa543d
pr-rules is a cursor rule published in the GitHub repository AdobeDocs/ff-services-docs (4 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 1,041 tokens to every session, about $0.0042 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-08-31.
Other cursor rules, from other repositories
rebase-only-merged-agents
When rebasing after a merge, only rebase the agents whose branches you just merged. Do not rebase agents that are still running.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
git-workflow
Rules for git operations, commit strategy, and GitHub CLI usage.
release-checklist
What to update with each code change or version release.
git-workflow
Git commit format and PR process - conventional commits.
branching-merging-strategy
This is a set of instructions to the AI Assistant for branching and merging strategy.