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/JasonColapietro/suede-creator-skillsWrote 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/jasoncolapietro/suede-creator-skills/suede-agent-workflows)<a href="https://agentmods.dev/plugins/jasoncolapietro/suede-creator-skills/suede-agent-workflows"><img src="https://agentmods.dev/badge/plugins/jasoncolapietro/suede-creator-skills/suede-agent-workflows/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/jasoncolapietro/suede-creator-skills/suede-agent-workflows"><img src="https://agentmods.dev/badge/plugins/jasoncolapietro/suede-creator-skills/suede-agent-workflows.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
suede-agent-workflows 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": "suede-agent-workflows",
"source": "./skills",
"strict": false,
"skills": [
"./suede-graph-flo-xr",
"./suede-ship-copy",
"./suede-agent-teams",
"./suede-workflow-skills",
"./suede-ai-eval"
],
"agents": [
"./suede-graph-flo-xr/agents/suede-graph-flo-xr-scout.md",
"./suede-graph-flo-xr/agents/suede-graph-flo-xr-code-reader.md",
"./suede-graph-flo-xr/agents/suede-graph-flo-xr-web-reader.md",
"./suede-graph-flo-xr/agents/suede-graph-flo-xr-patch-author.md",
"./suede-graph-flo-xr/agents/suede-graph-flo-xr-applier.md",
"./suede-graph-flo-xr/agents/suede-graph-flo-xr-verifier.md"
],
"description": "Multi-agent orchestration subset: search competing plans and ship one selected repo change through the Suede Thought Graph DAG (suede-graph-flo-xr), coordinate build lanes with quality gates and a signed handoff (suede-agent-teams), route cross-surface work end to end (suede-workflow-skills), and turn AI features into eval specs and acceptance gates (suede-ai-eval)."
}What it installs
The manifest is a name and a version. 5 skills, 6 agents travel with it, and installing the plugin installs all of them — 1,122 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill suede-ship-copy A 187 tokens
- Skill suede-agent-teams A 175 tokens
- Skill suede-graph-flo-xr A 160 tokens
- Skill suede-ai-eval A 172 tokens
- Skill suede-workflow-skills A 212 tokens
- Agent suede-graph-flo-xr-code-reader A 38 tokens
- Agent suede-graph-flo-xr-patch-author A 37 tokens
- Agent suede-graph-flo-xr-scout A 35 tokens
- Agent suede-graph-flo-xr-verifier A 30 tokens
- Agent suede-graph-flo-xr-web-reader A 41 tokens
- Agent suede-graph-flo-xr-applier A 35 tokens
What ships with it
2 files beside marketplace.json#suede-agent-workflows 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 Changed 04ca8c6023fa
- 1mo ago First seen · 21 lines scan A bb5e6785d372
suede-agent-workflows is a plugin published in the GitHub repository JasonColapietro/suede-creator-skills (125 stars, last pushed today), 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-09-03.
Other plugins, from other repositories
dark-factory
Curie's default dark factory agent: one labelled GitHub issue in, one reviewed pull request or one stated reason out. One agent reads the issue through the platform's getissue tool, pins acceptance criteria, plans, gets the plan reviewed by an Opus plan-reviewer subagent, writes a failing test where feasible, implemen.
github-activity
Read-only GitHub activity reporter for program managers. One hosted connector reads merged pull requests, opened and closed issues, and milestone movement across several repositories since a point in time. It holds no write tool, the tool policy allows only the read tool so anything else fails closed, and the…
divisible-work
Coordinates verified work using GPT-6.1 Sol or GPT-6 Luna, preferring permitted same-project Codex chats with native subagents as a portable fallback.
claude-code-pm
Autonomous Project Manager for Claude Code. Orchestrates parallel worker sessions to execute Linear tasks through a structured lifecycle: fetch, assign, implement, verify, review, merge.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.
claude-plugins-official marketplace
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.