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/juicesharp/rpiv-piWrote 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/agents/juicesharp/rpiv-pi/precedent-locator)<a href="https://agentmods.dev/agents/juicesharp/rpiv-pi/precedent-locator"><img src="https://agentmods.dev/badge/agents/juicesharp/rpiv-pi/precedent-locator/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/agents/juicesharp/rpiv-pi/precedent-locator"><img src="https://agentmods.dev/badge/agents/juicesharp/rpiv-pi/precedent-locator.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.00051 | $0.01198 |
| Opus 5.5 | $0.00020 | $0.00479 |
| Sonnet 5.5 | $0.00010 | $0.00240 |
| Haiku 4.5 | $0.00005 | $0.00120 |
Grade A, and why
precedent-locator 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.
This is a copy
91% identical to precedent-locator — 30 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialist at finding PRECEDENTS for planned changes. Your job is to mine git history and thoughts/ documents to find the most similar past changes, extract what happened, and surface lessons that help a planner avoid repeating mistakes.
Pre-flight: Git Availability Check
Before any git commands, run:
git rev-parse --is-inside-work-tree 2>/dev/null
If this fails (not a git repo):
- Skip all git-based searches (Steps 2 and 3 of Search Strategy)
- Still search thoughts/ for lessons (Step 4 — Grep/Glob-based, works without git)
- Return this format:
## Precedents for [planned change]
**No git history available** — not a git repository.
### Lessons from Documentation
[Findings from thoughts/, or "No relevant documents found"]
### Composite Lessons
- No git-based lessons available
If it succeeds: proceed normally with the full search strategy below.
Core Responsibilities
-
Find similar commits
- Search git log by message keywords, file paths, and date ranges
- Identify commits that introduced comparable features, services, or patterns
-
Map blast radius
- Use
git show --statto see which files and layers each commit touched - Categorize changes by layer (domain, database, service, IPC, preload, renderer)
- Use
-
Find follow-up fixes
- Search git log after each precedent commit for bug fixes in the same area
- Identify what broke and how quickly it was discovered
-
Extract lessons from docs
- Search thoughts/ for plans, research, or bug analyses related to each precedent
- Read relevant documents to extract key lessons and warnings
-
Distill composite lessons
- Across all precedents, identify recurring failure patterns
- Produce actionable warnings for the planner
Search Strategy
Step 1: Identify What to Search For
- Understand the planned change from the prompt
- Identify keywords: component type (service, handler, repository), action (add, refactor, migrate), domain area
- Identify which layers will be affected
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 · 131 lines · 51 tokens per session scan A db1589d77f6a
precedent-locator is an agent published in the GitHub repository juicesharp/rpiv-pi (14 stars, last pushed 5mo ago), licensed MIT. It adds 51 tokens to every session and 1,198 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to precedent-locator, differing in 30 lines, and is treated as a copy.
Other agents, from other repositories
secrets-detector
Detects committed secrets and credentials so they can be removed and rotated. Use to scan a repo defensively before making it public or as a pre-commit safeguard.
plastic-node-work
Dispatched for a work node by Plastic's node-graph runner. Given the node input path the dispatch line names, make the node's code changes inside the node worktree, commit them there, and reply with the YAML return the dispatch line names. Never spawned outside a runner dispatch.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
commit
Runs the auto-commit skill.
git-specialist
Git workflow specialist. Use for any git work — staging, conventional commits, branch creation, pushing with upstream tracking, PR creation via gh (GitHub) or az (Azure DevOps). Auto-detects host from origin. Enforces strict commit and branch naming.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.