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/Ryuketsukami/agent-work-protocolWrote 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/ryuketsukami/agent-work-protocol/agent-work-protocol)<a href="https://agentmods.dev/plugins/ryuketsukami/agent-work-protocol/agent-work-protocol"><img src="https://agentmods.dev/badge/plugins/ryuketsukami/agent-work-protocol/agent-work-protocol/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/ryuketsukami/agent-work-protocol/agent-work-protocol"><img src="https://agentmods.dev/badge/plugins/ryuketsukami/agent-work-protocol/agent-work-protocol.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade 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 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.
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 it installs
The manifest is a name and a version. 1 hook travel with it, and installing the plugin installs all of them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago 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 4mo 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
arrow-maintenance
Scaling layer for linked-intent-dev. Tracks spec-to-code coherence across large projects via docs/arrows/ index. Includes brownfield bootstrap for mapping existing codebases.
lid-experimental
Experimental LID skills with opt-in installation and explicit lifecycle (promotion or retirement). Layers on top of linked-intent-dev and arrow-maintenance.
linked-intent-dev
Structured design-before-code workflow: HLD → LLD → EARS specs → Tests → Code.
superstack
An agent-based software-development system that guides work from a short request to a tested, demonstrated piece of software. It uses checkpoints for planning and verification and explains conclusions in plain language.
polygraph
A polygraph for your state machine. The agent does the hard part for you: it instruments your code, builds any test doubles needed to run it, and captures real execution traces — then has an LLM derive a transition-function spec from the source (default: a SAM v2 strict-profile module with named…
kb
Build and maintain LLM-powered knowledge bases as Obsidian wikis with compile, query, lint, and evolve workflows.