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/pawbytes/skill-suitesWrote 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/pawbytes/skill-suites/utility-tools)<a href="https://agentmods.dev/plugins/pawbytes/skill-suites/utility-tools"><img src="https://agentmods.dev/badge/plugins/pawbytes/skill-suites/utility-tools/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/pawbytes/skill-suites/utility-tools"><img src="https://agentmods.dev/badge/plugins/pawbytes/skill-suites/utility-tools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
utility-tools 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": "utility-tools",
"description": "Developer productivity tools for Claude Code — generate McKinsey-style HTML slide decks from marketing strategies, automate software releases with version bumping, changelog generation, git tagging, and GitHub release publishing. 3 skills for teams shipping fast.",
"source": "./",
"strict": false,
"skills": [
"./src/tools/paw-tools-setup",
"./src/tools/paw-tools-presentation",
"./src/tools/paw-tools-release"
]
}What it installs
The manifest is a name and a version. 3 skills travel with it, and installing the plugin installs all of them — 127 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside marketplace.json#utility-tools 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 First seen · 11 lines scan A 22b5a96bf2f1
utility-tools is a plugin published in the GitHub repository pawbytes/skill-suites (114 stars, last pushed 15d 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-09-03.
Other plugins, from other repositories
workflow
Git and GitHub workflow skills — commits, branches, pull requests, issues, and CI actions.
oat-publish-python
Python release management: cleanup, version bump, uv build, GitHub release, publish monitoring.
oat-publish-rust
Rust crate/workspace release: verification gates, version bump, signed tag, CI or direct crates.io publish.
atlas-publish
Takes the open PRs of the Atlas/Bella monorepo to a registered draft release on either the over-the-air or the App Store lane, classifying between them from the expo-updates native fingerprint rather than from intent — ios.buildNumber sits inside that fingerprint, so a buildNumber bump alone forces a store release.…
ooda-loop marketplace
Plugin marketplace listing 1 plugin: ooda-loop.
essentials
Essential shipping workflow — group a dirty working tree into clean commits, push the branch, and open a senior-engineer-quality GitHub PR with auto-applied labels and "might address #X" issue links.