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/mhattingpete/claude-skills-marketplaceWrote 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/mhattingpete/claude-skills-marketplace/engineering-workflow-plugin)<a href="https://agentmods.dev/plugins/mhattingpete/claude-skills-marketplace/engineering-workflow-plugin"><img src="https://agentmods.dev/badge/plugins/mhattingpete/claude-skills-marketplace/engineering-workflow-plugin.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
engineering-workflow-plugin 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 8d 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": "engineering-workflow-skills",
"version": "1.2.0",
"description": "Skills for software engineering workflows: git operations, test fixing, code review, feature planning, and ensemble problem solving (generates multiple solutions in parallel and selects the best)",
"author": {
"name": "mhattingpete",
"email": "[email protected]"
}
}
What it installs
The manifest is a name and a version. 5 skills, 1 command, 1 agent travel with it, and installing the plugin installs all of them — 276 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.
- 8d ago First seen · 10 lines scan A 01fa1f88522a
engineering-workflow-plugin is a plugin published in the GitHub repository mhattingpete/claude-skills-marketplace (671 stars, last pushed 1mo ago), licensed Apache-2.0. 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-30.
Other plugins, from other repositories
maintainer-suite
Optional maintainer toolkit for skill review, repository publication, releases, and project announcements.
prflow
Turn feature requests into review-ready pull requests: issue, implementation, tests, a review-and-fix loop, and docs. Runs locally or on GitHub Actions, and is built for complex brownfield repos. Each week its retrospective reads what you actually merged and proposes improvements to your skill extensions.
technical-deslop
Clean branch/staged diffs by removing AI-style slop and restoring repo-consistent style without changing behavior.
review-agents
Specialist review subagents for Java/Maven projects — code review, test running, and dependency/CVE auditing on lighter model tiers. No-write by construction: Write and Edit are withheld, so they read, build, and report without touching the working tree.
ticket-triage
Backlog-drain loop: rank the open tickets, dispatch the genuinely startable ones in parallel (worktree-isolated, role-briefed, honest width), verify and merge each result, and re-triage on every completion until the queue is empty or everything left needs the user.
implement-issue
Drive a GitHub issue from branch to pull request with a language and build-tool agnostic workflow.