lpm-config

lpm-config is a skill for Codex from gug007/lpm. It costs 91 tokens per session (1,169 once invoked), scanned A, original, MIT.

A configuration skill for lpm, a macOS project-management tool, using YAML files to describe projects, services, actions, terminals, profiles, worktrees, and remote projects.

In plain words
What is it for?
Use it to create or edit .lpm.yml files, add services, actions, buttons, terminals, profiles, SSH projects, templates, and shared configuration layers.
Why use it?
It helps change lpm settings safely without directly editing live configuration files. It validates proposed changes before applying them.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it to create or edit .lpm.yml files, add services, actions, buttons, terminals, profiles, SSH projects, templates, and shared configuration layers.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gug007/lpm/lpm-config
Install

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.

Any agent
npx skills add gug007/lpm --skill lpm-config
Clone the repo
git clone --depth 1 https://github.com/gug007/lpm

Made for: Codex.

Wrote 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.

agentmods badge for lpm-config

README.md
[![agentmods](https://agentmods.dev/badge/skills/gug007/lpm/lpm-config.svg)](https://agentmods.dev/skills/gug007/lpm/lpm-config)
Your own site
<a href="https://agentmods.dev/skills/gug007/lpm/lpm-config"><img src="https://agentmods.dev/badge/skills/gug007/lpm/lpm-config.svg" alt="Measured on agentmods" height="20"></a>
Per session 91 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,169 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Rogue Agent · line 4
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00091 $0.01169
Opus 5 $0.00046 $0.00584
Sonnet 5 $0.00018 $0.00234
Haiku 4.5 $0.00009 $0.00117

Measured 8d ago against content hash 1ef925e6f12e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

lpm-config 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 8d 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.

lpm-config/SKILL.md · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Configure lpm

Create and modify lpm config on macOS exclusively through lpm config get and lpm config apply. Never modify a live project, repo, global, or template config directly with an editor, filesystem tool, patch, redirection, or script. The CLI validates the candidate before the app atomically replaces the destination.

Load only the relevant reference

  • Read references/core.md for project identity, services, dependencies, profiles, duplicates, linked Git worktrees, and project creation.
  • Read references/actions.md when adding or changing actions, buttons, terminals, inputs, ports, shortcuts, or nested menus.
  • Read references/sharing.md for .lpm.yml, global config, templates, extends, layering, and sparse overrides.
  • Read references/ssh.md for remote projects or mode: sync.
  • Read references/validation.md before preparing a candidate and follow its transactional workflow.

Resolve the target

Honor an explicit project or layer from the user. Otherwise run:

lpm config resolve --cwd . --json

Interpret the result:

  • One match: use the returned project name with lpm config get; never edit the returned path.
  • Multiple matches: ask which candidate to use.
  • No match: offer to create a project for the current directory or configure one of the returned available projects.

Use these explicit layer overrides:

  • “globally” or “all my projects” → ~/.lpm/global.yml
  • “share with the team”, “check it in”, or “for everyone” → <root>/.lpm.yml
  • “template” or “reuse across projects” → ~/.lpm/templates/<name>.yml

When lpm config resolve is unavailable, inspect the YAML project files read-only. Match the current directory against expanded root paths by path components; the deepest root wins. Do not parse YAML with line-oriented tools and do not write a config without lpm config apply.

Choose the shape

Read the full file on GitHub · 89 lines

Files

What ships with it

7 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.

Changes

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.

  1. 8d ago First seen · 89 lines · 91 tokens per session scan A 1ef925e6f12e

Subscribe to this mod's changes

lpm-config is a skill published in the GitHub repository gug007/lpm (159 stars, last pushed yesterday), licensed MIT. It adds 91 tokens to every session and 1,169 once invoked, about $0.0005 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.