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/0xNyk/lacpWrote 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/0xnyk/lacp/plugin)<a href="https://agentmods.dev/plugins/0xnyk/lacp/plugin"><img src="https://agentmods.dev/badge/plugins/0xnyk/lacp/plugin/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/0xnyk/lacp/plugin"><img src="https://agentmods.dev/badge/plugins/0xnyk/lacp/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lacp-hardening 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.
What it actually says
{
"name": "lacp-hardening",
"version": "1.0.0",
"description": "Production hardening for AI coding agents — quality gates, security guards, continuous QA, and session memory. From the LACP (Local Agent Control Plane) framework.",
"author": {
"name": "Nyk",
"url": "https://github.com/0xNyk"
},
"homepage": "https://github.com/0xNyk/lacp",
"repository": "https://github.com/0xNyk/lacp",
"license": "MIT",
"keywords": ["quality-gate", "security", "hardening", "memory", "hooks", "production", "testing", "guardrails"]
}
What it installs
The manifest is a name and a version. 3 skills, 1 command travel with it, and installing the plugin installs all of them — 238 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json 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.
- 1mo ago First seen · 14 lines scan A af3660b1e044
lacp-hardening is a plugin published in the GitHub repository 0xNyk/lacp (305 stars, last pushed 24d 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
openrig-core
OpenRig canonical skills and hooks for cross-runtime agent topology coordination, continuity, and operating discipline.
ideal-harness
Control plane around a stateless model: guard (deny-wins policy), compress (cache-safe toolresult compression), memory (code-graph + episodic), orchestrate (task ledger + subagent flow), web (SSRF-guarded fetch + live package docs), core (loader/validation/skills).
harness-self-improvement
SIPS graph runtime and home-base for bounded task execution, memory fabric recall, verification, delegation, and lifecycle automation.
modelharness
Fable 5 behavioral patterns as a harness for Opus 4.8: grounded progress, self-verification loops, delegation triggers, file-based memory, autonomy calibration. Zero-config: installs a SessionStart hook; skills auto-trigger.
tree-ring-memory
Local-first memory lifecycle, project bootstrap, and receipt-backed harness guidance for Claude Code using Tree Ring Memory v0.15+.
kage
Kage manages your memory and agents. It briefs and runs agents in isolated git worktrees for a single run or a multi-wave goal, re-runs the checks itself instead of trusting the agent's report, and remembers what it learns so each brief is smarter than the last.