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/penwyp/claudepreference/local-project-runtimenpx skills add penwyp/ClaudePreference --skill local-project-runtimegit clone --depth 1 https://github.com/penwyp/ClaudePreferenceWrote 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/penwyp/claudepreference/local-project-runtime)<a href="https://agentmods.dev/skills/penwyp/claudepreference/local-project-runtime"><img src="https://agentmods.dev/badge/skills/penwyp/claudepreference/local-project-runtime.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.00041 | $0.00928 |
| Opus 5 | $0.00020 | $0.00464 |
| Sonnet 5 | $0.00008 | $0.00186 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
local-project-runtime 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Local Project Runtime
Use this skill to turn an unknown repository into a locally manageable project with predictable build, start, test, logs, health, and cleanup commands.
Core Workflow
-
Inspect first:
- Read root docs and manifests:
README*,AGENTS.md,package.json, lockfiles,Dockerfile, Compose files, Makefile, task runner configs, CI workflows. - Identify the package manager, runtime, service entrypoint, frontend directories, backend directories, DB/external dependencies, default ports, and health endpoints.
- Check current worktree state before editing.
- Read root docs and manifests:
-
Reproduce narrowly:
- Run the smallest relevant command for the reported failure.
- Capture the exact failing phase: dependency install, typecheck/compile, frontend bundle, Docker image build, container boot, health probe, migration, or test runner.
- Prefer targeted checks before repo-wide verification.
-
Fix architecture, not symptoms:
- Keep build/start/test contracts in one local runtime surface, normally
deploy/local/. - Avoid one-off shell notes that cannot be rerun.
- Make generated scripts explicit, idempotent, and safe when services are absent.
- Keep build/start/test contracts in one local runtime surface, normally
-
Add or repair a lifecycle manager:
- Required commands:
init,deps,build,test,image,start,apply,restart,stop,status,logs,ps,clean,doctor. startcreates services and waits for health.applyrebuilds the image and force-recreates the service.restartrestarts an existing container; if none exists, it must start instead of doing an empty restart.statusmust show Compose state and HTTP health.cleanmust stop services and remove local runtime data only.
- Required commands:
-
Add build acceleration where justified:
- For Node/monorepos, add a local build wrapper that hashes frontend inputs and skips frontend production bundling when unchanged.
- Preserve correctness by hashing lockfiles, frontend source/config/public assets, and shared packages imported by the frontend.
- For Docker, split frontend build into its own layer before backend/application
COPY . .so backend-only changes reuse frontend layers. - Update
.dockerignoreto exclude local build artifacts and caches.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 68 lines · 41 tokens per session scan A 5cbda9a20afb
local-project-runtime is a skill published in the GitHub repository penwyp/ClaudePreference (137 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 928 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…