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 jszmajda/lid --skill lid-coachgit clone --depth 1 https://github.com/jszmajda/lidWrote 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/jszmajda/lid/lid-coach)<a href="https://agentmods.dev/skills/jszmajda/lid/lid-coach"><img src="https://agentmods.dev/badge/skills/jszmajda/lid/lid-coach/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/jszmajda/lid/lid-coach"><img src="https://agentmods.dev/badge/skills/jszmajda/lid/lid-coach.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00117 | $0.10781 |
| Opus 5.5 | $0.00047 | $0.04312 |
| Sonnet 5.5 | $0.00023 | $0.02156 |
| Haiku 4.5 | $0.00012 | $0.01078 |
Grade A, and why
lid-coach 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 13d 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 — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LID Coach
Reviews a project's current LID usage against LID's own principles and produces a prioritized set of recommendations. The posture is advisory: the project works; this skill tells the user where patterns are drifting from LID's principles or leaving value on the table.
This skill is invoked only by the /lid-coach command. It does not auto-trigger — a principle review reads a broad slice of the project and would be wasteful to fire opportunistically.
What this skill is not
- Not a configuration reconciler. That is
/update-lid. When a finding implies a configuration change, point the user there. - Not a structural auditor. That is
/arrow-maintenance(when the overlay is installed). When a finding is structural in nature — orphans, reverse orphans, adjacent-level coherence,index.yamldrift — surface the pattern and recommend/arrow-maintenancefor the precise enumeration. Do not attempt to enumerate structural instances from sampled reads. - Not a file editor. Advisory posture is load-bearing. Produce the report; the user applies.
Dispatch
On invocation, inspect the project and take exactly one of these actions:
| Detected state | Action |
|---|---|
No instruction file (the project's AGENTS.md, or CLAUDE.md under Claude Code) and no LID-shaped artifacts anywhere in the project (no HLD, no LLDs, no specs, no arrow overlay) |
Inform the user the project is not LID-configured; recommend /update-lid. Do not proceed with coaching. |
| The instruction file absent or missing LID directives but the project has LID-shaped artifacts (see threshold below) | Proceed with a full review anchored on the existing artifacts (default Full mode). Surface the missing (or precursor-named) instruction-file directives as a high-priority finding recommending /update-lid to reconcile. |
LID directives present, but docs/intent/ or docs/high-level-design.md is missing |
Proceed with a reduced review of what exists. Surface each missing piece as a high-priority finding and recommend /update-lid to reconcile. |
Scoped mode with missing or empty ## LID Scope |
Surface the misconfiguration as a high-priority finding. Run a conservative project-wide review treating all paths as in-scope. |
docs/arrows/index.yaml present but cannot be parsed |
Flag corruption to the user before any principle review. Offer either to proceed with a reduced review treating the overlay as absent, or to pause for the user to repair. |
| Fully configured (directives + mode marker + standard directories; Scoped with valid scope) | Proceed with a full review. |
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.
- 13d ago Changed · -41 lines scan B → A 873d7e81a8f0
- 1mo ago First seen · 342 lines · 117 tokens per session scan B 1096618f9b73
lid-coach is a skill published in the GitHub repository jszmajda/lid (115 stars, last pushed yesterday), licensed MIT. It adds 117 tokens to every session and 10,781 once invoked, about $0.0005 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
user-docs
Write user documentation for a project by scanning its codebase — its UI screens and its public API/CLI — inferring what someone can actually do with it, and drafting brief, task-oriented docs to the Diátaxis standard (tutorial / how-to / reference / explanation). Handles both non-technical end-user docs and developer…
add
Create a new Clawness rule from a natural language description. Describe what you want enforced and this will generate the YAML rule file with proper tags, triggers, and examples.
messaging
Write or rewrite the product's customer-facing copy — landing page, hero section, CTAs, onboarding, empty states, pricing, app-store and marketing pages — with the customer as the hero and the product as their guide. Scans the existing UI copy, drafts a one-page message brief (who the customer is, what they want, the…
review
Run an adversarial code review on staged changes or a specific file. Spawns the code-critic agent to find bugs, performance issues, and missed edge cases. Use before merging PRs or committing.
perf
Run a performance audit on the project or a specific module. Checks for N+1 queries, unnecessary re-renders, memory leaks, bundle size issues, and slow algorithms.
oneshot
End-to-end autonomous workflow — research, plan, implement, validate, ship, and merge in one command. ALWAYS use when the user says 'oneshot', 'do everything end to end', 'full workflow', or wants to go from ticket/idea to merged PR autonomously. All phases run sequentially in the current session, using agent teams…