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/marketplacegit clone --depth 1 https://github.com/shrekshrek/project-workflowGrade A, and why
project-workflow marketplace 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",
"owner": {
"name": "shrek.wang"
},
"metadata": {
"description": "project-workflow v3 — spec-driven feature development blueprint for AI-assisted coding"
},
"plugins": [
{
"name": "project-workflow",
"source": {
"source": "git-subdir",
"url": "https://github.com/shrekshrek/project-workflow.git",
"path": "claude/project-workflow",
"ref": "plugin-dist"
},
"description": "Spec-driven feature development plugin (Claude Code-native). 9 skills (/project-init, /project-personalize, /feature-init, /spec-quality-check, /spec-revise, /feature-done, /feature-archive, /spec-reconcile, /agents-md-revise) + 6 sub-agents (agents-md-reviewer, spec-reviewer, spec-quality-reviewer, tech-researcher, codebase-explorer, decision-completeness-auditor).",
"author": {
"name": "shrek.wang"
},
"homepage": "https://github.com/shrekshrek/project-workflow",
"repository": "https://github.com/shrekshrek/project-workflow",
"license": "MIT",
"keywords": ["spec-driven", "workflow", "blueprint", "agents-md"],
"category": "workflow"
}
]
}
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 · 30 lines scan A 0199a35d690e
project-workflow marketplace 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
gsd-core
GSD Core is a meta-prompting, context engineering, and spec-driven development system for AI coding agents.
Citadel
Claude Code harness for routing requests, preserving run state, enforcing hooks, and recording evidence.
stop-that-shit
Keep Claude Code on task with local-first mode, scope, dependency, hash, and delegation guardrails.
ck
Cavekit — compressed spec-driven dev. Full loop (grill → spec → research → review → build) over one SPEC.md file: three core commands + four reach-for. Caveman encoding. Bug-to-spec backprop.
allium
Velocity through clarity.
zapier
Connect 9,000+ apps to your AI workflow. Discover, enable, and execute Zapier actions directly from your client.