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 agentmods add settings/alieismy/codex-three-layer-delivery/settingsgit clone --depth 1 https://github.com/alieismy/codex-three-layer-deliveryWrote 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/settings/alieismy/codex-three-layer-delivery/settings)<a href="https://agentmods.dev/settings/alieismy/codex-three-layer-delivery/settings"><img src="https://agentmods.dev/badge/settings/alieismy/codex-three-layer-delivery/settings.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
codex-three-layer-delivery 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 3d 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
{
"attribution": {
"commit": "",
"pr": "",
"sessionUrl": false
},
"enableAllProjectMcpServers": false,
"permissions": {
"deny": [
"Read(./.env)",
"Read(./secrets/**)"
],
"ask": [
"Bash(git commit *)",
"Bash(git push *)",
"Bash(git tag *)",
"Bash(npm publish *)",
"Bash(rm *)"
]
}
}
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.
- 3d ago First seen · 22 lines scan A 5bca8c19d8c0
codex-three-layer-delivery is a settings file published in the GitHub repository alieismy/codex-three-layer-delivery (2 stars, last pushed 10d 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-31.
Other settings, from other repositories
supabase
Agent settings declaring 2 hook events (SessionStart, PostToolUse).
superset
Agent settings declaring 1 hook event (PreToolUse).
claude-cookbooks
Agent settings declaring 2 hook events (SessionStart, PreToolUse).
claude-code-best-practice
Agent settings declaring 30 hook events (PreToolUse, PermissionRequest, PostToolUse, PostToolUseFailure) and 24 allowed tools.
electron
Agent settings declaring 17 allowed tools.
uv
Agent settings declaring 2 hook events (SessionStart, PostToolUse).