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 skills/re-cinq/lore-oss/lore-prnpx skills add re-cinq/lore-oss --skill lore-prgit clone --depth 1 https://github.com/re-cinq/lore-ossWrote 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/re-cinq/lore-oss/lore-pr)<a href="https://agentmods.dev/skills/re-cinq/lore-oss/lore-pr"><img src="https://agentmods.dev/badge/skills/re-cinq/lore-oss/lore-pr.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.00026 | $0.00443 |
| Opus 5 | $0.00013 | $0.00221 |
| Sonnet 5 | $0.00005 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
lore-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 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.
What it actually says
You are drafting a PR description. Read everything yourself. Do not ask the developer to gather information.
Read automatically (do not ask for any of this)
- Feature spec: find the relevant
specs/*/spec.mdfrom the branch name or changed files (look for the feature slug in the path) - Changed files:
git diff --stat mainandgit diff main(skim for key changes) - ADRs referenced by the feature (check
adrs/orspecs/*/research.md) - Task completion: check
specs/*/tasks.mdfor what's done vs remaining - Repo conventions: CLAUDE.md (if exists)
Draft the description
Fill every section of the PR template (if .github/PULL_REQUEST_TEMPLATE.md
exists, follow its structure). Otherwise use:
## Why
[What problem this solves — from spec problem statement]
## What Changed
[Summary of changes — from git diff analysis]
## Alternatives Considered
[From spec or research.md — what was rejected and why]
## ADRs & Architecture
[Any architectural decisions made or referenced]
## Spec
[Link to specs/{feature}/spec.md]
## Testing
[What was tested, how to verify]
Be specific. Write what a future engineer reading this in 18 months needs to understand. Do not write "improves X" or "adds Y feature." Write what problem it solves, what was rejected and why, what constraints shaped the approach.
If no alternatives-rejected section exists anywhere, ask one question: "What other approaches did you consider and why not?" Wait for the answer before finishing.
Output format
Show the complete draft in a code block so the developer can copy it. After showing: "Does this look right? Anything to change?"
After confirmation
Create the PR:
git push -u origin HEAD
gh pr create --title "..." --body "..."
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 · 64 lines · 26 tokens per session scan A 7287a8afdd27
lore-pr is a skill published in the GitHub repository re-cinq/lore-oss (11 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 26 tokens to every session and 443 once invoked, about $0.0001 per session on Opus 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…