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.
/plugin marketplace add podlayer/message-drop-sentinelnpx agentmods add plugins/podlayer/message-drop-sentinel/marketplacegit clone --depth 1 https://github.com/podlayer/message-drop-sentinelGrade A, and why
podlayer 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 yesterday.
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": "podlayer",
"owner": { "name": "Podlayer", "url": "https://podlayer.ai" },
"plugins": [
{
"name": "message-drop-sentinel",
"source": "./",
"description": "Detects Claude Code's silent mid-turn message drops and provides a delivery channel the bug can't touch"
}
]
}
What ships with it
1 file beside marketplace.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.
- yesterday First seen · 12 lines scan A 94f97a0acc38
podlayer is a plugin published in the GitHub repository podlayer/message-drop-sentinel (1 stars, last pushed 27d 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 plugins, from other repositories
ai-engineer
Use this agent when implementing AI/ML features, integrating language models, building recommendation systems, or adding intelligent automation to applications. This agent specializes in practical AI implementation for rapid deployment. Examples:\n\n \nContext: Adding AI features to an app\nuser: "We need AI-po.
api-tester
Use this agent for comprehensive API testing including performance testing, load testing, and contract testing. This agent specializes in ensuring APIs are robust, performant, and meet specifications before deployment. Examples:\n\n \nContext: Testing API performance under load.
app-starter
Bootstrap new Next.js, Flutter, and FastAPI apps with current packages, no deprecated APIs, and a consistent house style. Ships skills nextjs-app, flutter-app, and fastapi-app.
adamsreview
Multi-lens code review pipeline: deep review (Claude or Codex), automated fix loop, interactive walkthrough, manual promote, external-finding injection.
instructions-audit
A prompt-injection tripwire for instruction files. An InstructionsLoaded hook audits CLAUDE.md / .claude/rules/.md content as it enters context and flags hidden or hostile directives: invisible Unicode smuggling (zero width characters, tag characters, variation-selector runs; the TrapDoor supply-chain signature), bidi.
agent-decision-record
Structured decision-making for AI coding agents. Creates auditable Agent Decision Records (AgDR) when technical choices are made.