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 Ryuketsukami/agent-work-protocolnpx agentmods add plugins/ryuketsukami/agent-work-protocol/agent-work-protocolgit clone --depth 1 https://github.com/Ryuketsukami/agent-work-protocolGrade A, and why
agent-work-protocol 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": "agent-work-protocol",
"version": "1.0.0",
"description": "An always-on operating protocol for coding agents: build only what's asked, surface ambiguity as Q/A/P/E/X, scale process to task size, and verify before claiming. Injected into every session via a SessionStart hook.",
"author": {
"name": "Ryuketsukami",
"url": "https://github.com/Ryuketsukami"
},
"homepage": "https://github.com/Ryuketsukami/agent-work-protocol",
"repository": "https://github.com/Ryuketsukami/agent-work-protocol",
"license": "MIT",
"keywords": [
"claude-code",
"agent",
"protocol",
"workflow",
"hooks",
"agentic-coding",
"guardrails"
]
}
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.
- yesterday First seen · 22 lines scan A 9c9aac7c0e7c
agent-work-protocol is a plugin published in the GitHub repository Ryuketsukami/agent-work-protocol (1 stars, last pushed 3mo 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
claude-code-tips
Developer experience essentials: GitHub Actions debugging, conversation half/quarter-cloning, context handoffs, research (Reddit and Hacker News), private GitHub search, and Claude Code version checks.
research-git
A memory system for the code you're exploring: capture each idea as a semantic Feature Capsule, recall it, and regenerate it onto today's codebase. Segmentation/regeneration run on natively-dispatched subagents (your subscription) — no pay-per-use API. MCP serves the graph read-only for sharing.
the-loop
Plugin marketplace listing 1 plugin: the-loop.
the-loop
An opinionated product-development-lifecycle harness that lets coding agents deliver work items end-to-end, with minimal human intervention, through a predictable loop of plan, execute, self-review, critic-review and escalate.
exosuit
Suit up. Build anything. A full engineering organization for Claude Code — deep idea interrogation, TDD sprints, enforced quality gates. 43 skills, 8 agents, 13 hooks, path-scoped rules.
claude-bestpractice
Enforcement, memory and parallel-session coordination for solo founders running several Claude Code sessions on one repository.