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/ryanzhao1011/workframeWrote 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/ryanzhao1011/workframe/workframe-launcher)<a href="https://agentmods.dev/plugins/ryanzhao1011/workframe/workframe-launcher"><img src="https://agentmods.dev/badge/plugins/ryanzhao1011/workframe/workframe-launcher/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/ryanzhao1011/workframe/workframe-launcher"><img src="https://agentmods.dev/badge/plugins/ryanzhao1011/workframe/workframe-launcher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
workframe-launcher 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 23d 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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "workframe-launcher",
"displayName": "Workframe Launcher",
"version": "1.1.0",
"description": "Workframe 启动器：一条命令开启全部流程。新建 Workframe 项目或接入已有项目——问清你的产品、提出模块结构、生成骨架、把项目订阅到 core 插件，并验证装机结果。每台机器装一次，它会替你把 core 装进每个项目。",
"author": {
"name": "Zhao Jiahao"
},
"homepage": "https://github.com/ryanzhao1011/workframe",
"repository": "https://github.com/ryanzhao1011/workframe",
"license": "MIT",
"keywords": [
"claude-code",
"claude-code-plugin",
"product-management",
"prd",
"agents",
"skills",
"hooks",
"project-memory",
"chinese"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 175 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 23d ago Changed 1adfd3798c53
- 1mo ago First seen · 25 lines scan A 662cda253be7
workframe-launcher is a plugin published in the GitHub repository ryanzhao1011/workframe (7 stars, last pushed 24d 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
pm-skills
Product manager skill suite for Claude Code — PRD writing, competitor research, daily briefing, HTML prototyping, feature acceptance, UI walkthrough.
goal-by-goal
Convert any feature idea, plan, PRD, or brief into a sequenced goal-by-goal execution document with reviewer-gated commits — for everyday feature development, MVPs, migrations, and refactors. Generates a project brief, per-goal scope/tasks/acceptance criteria, an LLM-reviewer prompt, a progress tracker, and a reviews…
fleetdeck
Localhost fleet board for Claude Code, guarded by a release-bound compatibility policy.
unfurl-context
Unfurls Jira tickets, GitHub PRs/issues/repos/files, GitLab issues/MRs/projects/files, and Sentry issues referenced in your prompt into context Claude can read.
pr-workflow
PR and issue lifecycle — structured planning (CEO/Eng gates), PR creation, code review, issue triage, session handoffs.
handoff
Portable project memory + development workflow for coding agents: auto-loads STATUS+RULES each session, enforces folder-level CONTEXT.md on edit, nudges durable state updates at turn end, scaffolds the system into any repo via guided discovery, and ships a tiered 6-phase workflow skill set covering every phase (brief.