LazyCodex is an agent harness for working on complex codebases, combining project memory, planning, execution, and completion checks inside Codex. It is for developers who want structured, repeatable assistance when handling substantial software projects. The catalogue contains the skills, hook, and MCP integration that provide its workflow inside Codex.
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 skills add code-yeongyu/lazycodex --skill lspgit clone --depth 1 https://github.com/code-yeongyu/lazycodexWrote 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/code-yeongyu/lazycodex/lsp)<a href="https://agentmods.dev/skills/code-yeongyu/lazycodex/lsp"><img src="https://agentmods.dev/badge/skills/code-yeongyu/lazycodex/lsp/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/skills/code-yeongyu/lazycodex/lsp"><img src="https://agentmods.dev/badge/skills/code-yeongyu/lazycodex/lsp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00027 | $0.00309 |
| Opus 5.5 | $0.00011 | $0.00124 |
| Sonnet 5.5 | $0.00005 | $0.00062 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
lsp 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- lsp — 100% identical, 0 lines differ
What it actually says
Codex LSP
Call lsp MCP tools through the tool interface; lsp.*/mcp__lsp__* are tool-call names, not shell commands.
Tools
lsp.status: list configured, installed, missing, disabled, and active language servers.lsp.diagnostics: check one file or directory for LSP diagnostics. Preferseverity: "error"after edits.lsp.goto_definition: locate a symbol definition from file, line, and character.lsp.find_references: find usages of a symbol across the workspace.lsp.symbols: inspect document symbols or search workspace symbols.lsp.prepare_rename: check whether a rename is valid at a position.lsp.rename: apply a language-server workspace edit for a rename.
Config
Project config lives at .codex/lsp-client.json; user config lives at ~/.codex/lsp-client.json.
{
"lsp": {
"typescript": {
"command": ["typescript-language-server", "--stdio"],
"extensions": [".ts", ".tsx", ".js", ".jsx"]
}
}
}
Use lsp.status first when diagnostics report a missing language server.
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 · 36 lines · 27 tokens per session scan A 3fab0f09a4df
lsp is a skill published in the GitHub repository code-yeongyu/lazycodex (3,782 stars, last pushed 3d ago), licensed MIT. It adds 27 tokens to every session and 309 once invoked, about $0.0001 per session on Opus 5.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
code_explorer
Explores the repository to locate primary source files, coupled UI components, and test files for bug reports or feature requests.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
feedback
Skill "feedback" from Hmbown/Codewhale, covering feedback, when to use, setup, workflow and non-goals.
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…
smiles-validation
Strict SMILES validation, structural comparison, and modification verification. Catches invalid LLM-generated molecules.
oversight-team
Use when you are a seat on the oversight pod (a standing monitor-mode rig that keeps OTHER rigs healthy), configuring or running the drift detectors, or choosing whether to intervene vs escalate. Covers the pull-not-poll posture, the v0 detectors (premature-park, process-drift, off-task, token-burn), the intervention…