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/shrekshrek/project-workflowWrote 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/shrekshrek/project-workflow/claude)<a href="https://agentmods.dev/plugins/shrekshrek/project-workflow/claude"><img src="https://agentmods.dev/badge/plugins/shrekshrek/project-workflow/claude/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/shrekshrek/project-workflow/claude"><img src="https://agentmods.dev/badge/plugins/shrekshrek/project-workflow/claude.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
project-workflow 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 2d 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": "project-workflow",
"description": "Spec-driven feature development blueprint for AI-assisted coding (Claude Code-native). Skills: /project-init, /project-personalize, /feature-init, /spec-quality-check, /spec-revise, /feature-done, /feature-archive, /spec-reconcile, /agents-md-revise. Agents: agents-md-reviewer, spec-reviewer, spec-quality-reviewer, tech-researcher, codebase-explorer, decision-completeness-auditor.",
"version": "3.23.2",
"author": {
"name": "shrek.wang"
},
"homepage": "https://github.com/shrekshrek/project-workflow",
"repository": "https://github.com/shrekshrek/project-workflow.git",
"license": "MIT"
}
What it installs
The manifest is a name and a version. 9 skills, 6 agents travel with it, and installing the plugin installs all of them — 646 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill feature-init A 43 tokens
- Skill agents-md-revise A 30 tokens
- Skill feature-done A 28 tokens
- Skill project-personalize A 29 tokens
- Skill spec-quality-check A 42 tokens
- Skill spec-revise A 50 tokens
- Skill feature-archive A 25 tokens
- Skill spec-reconcile A 23 tokens
- Skill project-init A 45 tokens
- Agent agents-md-reviewer A 62 tokens
- Agent codebase-explorer A 53 tokens
- Agent decision-completeness-auditor A 59 tokens
- Agent spec-quality-reviewer A 69 tokens
- Agent spec-reviewer A 42 tokens
- Agent tech-researcher A 46 tokens
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.
- 2d ago Changed 0ddaf02c8933
- 11d ago Changed 4ef9dfd58867
- 1mo ago Changed 3f8a19f31a44
- 1mo ago Changed cdf2ae12602f
- 1mo ago Changed ccf535b59a09
- 1mo ago First seen · 12 lines scan A 3c88cdea049f
project-workflow is a plugin published in the GitHub repository shrekshrek/project-workflow (2 stars, last pushed 3d 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
specmanager
Lifecycle kanban for Claude Code projects (PRD → architecture → plan → tasks → walkthroughs).
hippo
hippocampus — perception and memory for coding agents: task registry, outcome ledger, and background clerks that turn transcripts into evidence. Records; never enforces. CLI and slash commands are hippo.
crew
A multi-agent dev harness: hand it a goal and the orchestrator triages, implements, reviews, responds to feedback, and keeps docs and knowledge current — autonomously, up to a review-ready PR. Use the individual skills directly, or /crew:run to let it decide what to do.
devforge-ai
Enterprise & Startup SDLC orchestration plugin: 10 agents across 5 phases (Plan, Build, Verify, Ship, Operate), 43 knowledge skills, 16 commands. Hyper-scale RCA, 7-tier test matrix, Stripe monetization, and dynamic autonomous routing.
manager
Product and project management discipline for the NVZver marketplace. Agents: product-manager — shapes vague ideas into structured draft pitches and returns their full content + pending human gates (writes no files); project-manager — stewards the roadmap, recommends what to build next with dependency/risk/value…
yonsei-rms
Summarize supplied RMS project data and audit its budget arithmetic or participant roles and periods without uploads, approvals, or submissions.