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/edloidas/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/edloidas/skills/workflow)<a href="https://agentmods.dev/plugins/edloidas/skills/workflow"><img src="https://agentmods.dev/badge/plugins/edloidas/skills/workflow/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/edloidas/skills/workflow"><img src="https://agentmods.dev/badge/plugins/edloidas/skills/workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
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 4d 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": "workflow",
"version": "5.18.0",
"description": "End-to-end workflows: one issue from analysis to merge, a batch of work orchestrated through subagents, the review queue, and the issue backlog",
"author": {
"name": "Mikita Taukachou",
"url": "https://edloidas.io"
},
"repository": "https://github.com/edloidas/skills",
"license": "MIT",
"keywords": [
"skills",
"workflow",
"issue",
"automation",
"lifecycle"
]
}
What it installs
The manifest is a name and a version. 4 skills travel with it, and installing the plugin installs all of them — 493 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.
- 4d ago Changed b4558297d84b
- 13d ago Changed 8c2faf857e30
- 14d ago Changed 80c2d7336095
- 16d ago Changed 267d6ca77ae7
- 21d ago Changed 7339659186aa
- 23d ago Changed 6274f46e5a05
- 24d ago Changed f18e65436c70
- 27d ago Changed 84672546df75
- 1mo ago Changed 9d9fb7809c8c
- 1mo ago First seen · 19 lines scan A e873e93eb18b
workflow is a plugin published in the GitHub repository edloidas/skills (2 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-08-31.
Other plugins, from other repositories
quality
Code quality skills — refactoring, naming conventions, project structure, and internationalisation.
forgedock
Autonomous AI development pipeline that uses GitHub as a structured knowledge graph for Claude Code agents. Adds /work-on, /review-pr, /quality-gate, /orchestrate, and 20+ pipeline commands.
oat-qa
Multi-agent QA audit: code quality, architecture, security, tests, CI/CD, docs.
ivuorinen-skills
Nitpicker — hostile audit toolkit: /nitpicker dispatches specialist audit commands (adversarial review, security, tests, docs, types, architecture, perf, reliability, caching, concurrency, error handling, leaks, deps, licensing, CI, commits, migrations, observability, API contracts, a11y, i18n, privacy, confi.
slopstop
Autonomous, ticket-anchored AI development for GitHub Issues, Linear, and JIRA, built on one idea: stop slop before it goes in, instead of reviewing it out afterwards. Work starts from a ticket, not a prompt. One command drives the whole lifecycle for one ticket or twenty at once, interleaved and unattended…
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.