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 shrekshrek/project-workflownpx agentmods add plugins/shrekshrek/project-workflow/claudegit clone --depth 1 https://github.com/shrekshrek/project-workflowGrade 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.20.2",
"author": {
"name": "shrek.wang"
},
"homepage": "https://github.com/shrekshrek/project-workflow",
"repository": "https://github.com/shrekshrek/project-workflow.git",
"license": "MIT"
}
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 First seen · 12 lines scan A 3c88cdea049f
project-workflow is a plugin published in the GitHub repository shrekshrek/project-workflow (2 stars, last pushed 2d 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
kashzod
KashZod's plugin catalog. Hosts devloop, a spec-plan-implement TDD loop with independent review-agent gates.
devloop
Spec, plan, implement, review: a test-driven development loop for AI coding agents. Three commands map to three gates, one per command (plus a convergence back-edge where /implement re-runs the plan gate): /spec (WHAT, spec validation), /plan (HOW, plan review), /implement (BUILD, conformance + adversarial red-team…
agent-toolkit
A collection of project-agnostic skills for common engineering tasks such as ticket refinement, planning, code reviews, agent memory hygiene, skill authoring, and more.
kit
Spec-driven Claude Code workflow with verification pipeline. Hooks, slash commands, and verification subagents.
llamaparse-mcp
Unlock document processing and Index v2 retrieval workflows with the LlamaParse Platform MCP.
sharp-edges
Identify error-prone APIs, dangerous configurations, and footgun designs that enable security mistakes.