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/100yenadmin/Lossless-Codex-Orchestrator-LCOWrote 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/100yenadmin/lossless-codex-orchestrator-lco/lco-recall)<a href="https://agentmods.dev/plugins/100yenadmin/lossless-codex-orchestrator-lco/lco-recall"><img src="https://agentmods.dev/badge/plugins/100yenadmin/lossless-codex-orchestrator-lco/lco-recall/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/100yenadmin/lossless-codex-orchestrator-lco/lco-recall"><img src="https://agentmods.dev/badge/plugins/100yenadmin/lossless-codex-orchestrator-lco/lco-recall.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lco-recall 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 19 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.
- 1mo ago First seen · 9 lines scan A c29aa1f05a5a
lco-recall is a plugin published in the GitHub repository 100yenadmin/Lossless-Codex-Orchestrator-LCO (33 stars, last pushed 2mo ago), with no licence file. 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
repobrain
Repository knowledge engine plugin. Bundles CLI-backed slash commands (rb-setup / rb-init / rb-refresh / rb-ask) plus the agent-repo-init skill. Works in both Claude Code and Codex CLI.
rembric
Memory for Claude Code, backed by your self-hosted Rembric server.
lockstep
Shared decision memory for teams building with AI coding agents: captures each decision once and briefs every agent before it acts.
ls-notes
Notes repository skills.
vibsync-mcp
Long-term team memory and live work context for AI coding agents.
rosetta
Reconcile every AI coding agent's conversations (Claude Code, Codex, Gemini, Cursor, Aider, opencode, Cline + 11 more) with git and docs into one cited ground truth, and distill durable ADR/PDR/BDR decision records.