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/hooks/100yenadmin/lossless-codex-orchestrator-lco/stop)<a href="https://agentmods.dev/hooks/100yenadmin/lossless-codex-orchestrator-lco/stop"><img src="https://agentmods.dev/badge/hooks/100yenadmin/lossless-codex-orchestrator-lco/stop/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/hooks/100yenadmin/lossless-codex-orchestrator-lco/stop"><img src="https://agentmods.dev/badge/hooks/100yenadmin/lossless-codex-orchestrator-lco/stop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
Stop 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 2mo ago.
A static scan of the commands this hook runs, not an audit. A hook is shell that executes on your machine at the event it names, which is why every command in it is printed with what was found.
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 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.
- 2mo ago First seen · 13 lines scan A 79aad8475ebf
Stop is a hook 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: a hook is shell that never enters the context. 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.
Stop compared with hooks from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| Stop100yenadmin/Lossless-Codex-Orchestrator-LCO | Hook | 33 | 2mo ago | none | A | — | Claude Code |
| SessionStartphenomenoner/Chatgpt-Codex-App-Plus | Hook | 2 | 11d ago | MIT | A | — | Claude Code |
| UserPromptSubmitphenomenoner/Chatgpt-Codex-App-Plus | Hook | 2 | 11d ago | MIT | A | — | Claude Code |
| PostToolUsephenomenoner/Chatgpt-Codex-App-Plus | Hook | 2 | 11d ago | MIT | A | — | Claude Code |
| SessionStartblasrodri/truth | Hook | 1 | 4mo ago | MIT | C | — | Claude Code |
| PreToolUsehehee9/codex-compressor | Hook | 10 | 5d ago | Apache-2.0 | A | — | Claude Code |
| PostToolUseFailureDorShaer/Husk | Hook | 16 | 2d ago | none | A | — | Claude Code |