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-featurenpx skills add re-cinq/lore-oss --skill lore-featuregit 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-feature)<a href="https://agentmods.dev/skills/re-cinq/lore-oss/lore-feature"><img src="https://agentmods.dev/badge/skills/re-cinq/lore-oss/lore-feature.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.00039 | $0.00860 |
| Opus 5 | $0.00019 | $0.00430 |
| Sonnet 5 | $0.00008 | $0.00172 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
lore-feature 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are helping a developer implement a feature. Do the work yourself. Ask one question at a time. Run commands yourself. Wait for confirmation only at decision points.
Two entry points
Entry A: Feature already has a spec (PM created it via Lore)
- List available specs:
ls specs/and show them. - Ask: "Which feature do you want to work on?" (or they already told you)
- Read the spec:
specs/{feature}/spec.md - Read the tasks:
specs/{feature}/tasks.md(if exists) - Read the data model:
specs/{feature}/data-model.md(if exists) - Show a summary: what the feature does, how many tasks, which are done.
- Ask: "Ready to start? I'll work through the tasks in order."
Entry B: New feature (no spec yet)
- Ask: "What do you want to build? Short description — what and why."
- Load repo context via
get_context(Lore MCP) to understand conventions. - Create the feature directory:
specs/{slug}/ - Write
specs/{slug}/spec.md— problem statement, user scenarios, functional requirements, success criteria. Match the style of existing specs in this repo. - Show the spec. Ask: "Does this capture what you want?"
- Write
specs/{slug}/tasks.md— checklist format:
Organized by phase. Mark parallelizable tasks with [P]. Include actual file paths from the repo structure.- [ ] T001 [P] Description with file path - [ ] T002 Description with file path - Show the tasks. Ask: "Does this breakdown look right?"
- Commit the spec files:
git add specs/{slug}/ && git commit
Implementation flow (both entry points)
Once the spec and tasks exist:
- Create a feature branch:
git checkout -b feat/{slug} - Find the first uncompleted task in
tasks.md - Show: "Working on T{N}: {description}"
- Implement the task — write code, create files, modify existing code. Follow the repo's conventions from CLAUDE.md.
- After completing the task, mark it done in tasks.md:
Change
- [ ] T{N}to- [x] T{N} - Commit the changes with a clear message referencing the task.
- Ask: "T{N} done. Continue to T{N+1}?" (or let them review first)
- Repeat until all tasks are done or developer stops.
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 · 78 lines · 39 tokens per session scan A 02860084359d
lore-feature is a skill published in the GitHub repository re-cinq/lore-oss (11 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 39 tokens to every session and 860 once invoked, about $0.0002 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…