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.
git 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/plugins/jszmajda/lid/lid-experimental)<a href="https://agentmods.dev/plugins/jszmajda/lid/lid-experimental"><img src="https://agentmods.dev/badge/plugins/jszmajda/lid/lid-experimental/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/plugins/jszmajda/lid/lid-experimental"><img src="https://agentmods.dev/badge/plugins/jszmajda/lid/lid-experimental.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lid-experimental 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 5d 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.
What it actually says
{
"name": "lid-experimental",
"description": "Experimental LID skills with opt-in installation and explicit lifecycle (promotion or retirement). Layers on top of linked-intent-dev and arrow-maintenance.",
"version": "0.3.0",
"author": {
"name": "Jess Szmajda"
},
"repository": "https://github.com/jszmajda/lid",
"license": "MIT"
}
What it installs
The manifest is a name and a version. 2 skills, 1 command travel with it, and installing the plugin installs all of them — 342 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 5d ago Changed 411f632c9dce
- 1mo ago First seen · 11 lines scan A 53e26012df6c
lid-experimental is a plugin published in the GitHub repository jszmajda/lid (112 stars, last pushed 3d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
clawness
Puts the right rules in context on every prompt, automatically — built for full-stack developers moving across frontend, backend, and SQL in one session, researchers working in bare or LaTeX-only directories, and teams who want adversarial review (security red/blue team, code critic) before merge. 222 rules across 30…
superstack
An agent-based software-development system that guides work from a short request to a tested, demonstrated piece of software. It uses checkpoints for planning and verification and explains conclusions in plain language.
agent-work-protocol
An always-on operating protocol for coding agents: build only what's asked, surface ambiguity as Q/A/P/E/X, scale process to task size, and verify before claiming. Injected into every session via a SessionStart hook.
catalyst-dev
Complete development workflow: research → plan → implement → validate → ship. Includes research agents, planning tools, handoff system, Linear integration, and PM commands.
catalyst-foundry
Setup, maintenance, and compounding upkeep of the Catalyst framework and the thoughts/ knowledge base: framework diagnostics/repair (setup-catalyst), terminal launcher config (setup-warp), and research-doc curation (research-curate). Future home for the compound-engineering retro/learning loop.
catalyst-legacy
Pre-phase-agent (wave-based) orchestration workflow preserved as a documented fallback: oneshot, orchestrate, god, setup-orchestrate. Superseded by catalyst-dev's execution-core/phase-agent pipeline. Requires catalyst-dev (shared backing scripts).