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/levnikolaevich/claude-code-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/levnikolaevich/claude-code-skills/delivery-suite)<a href="https://agentmods.dev/plugins/levnikolaevich/claude-code-skills/delivery-suite"><img src="https://agentmods.dev/badge/plugins/levnikolaevich/claude-code-skills/delivery-suite/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/levnikolaevich/claude-code-skills/delivery-suite"><img src="https://agentmods.dev/badge/plugins/levnikolaevich/claude-code-skills/delivery-suite.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
delivery-suite 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 29d 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": "delivery-suite",
"description": "Publish the intended changes and verify what reached the remote repository or target environment.",
"source": "./plugins/delivery-suite",
"strict": false
}What it installs
The manifest is a name and a version. 4 skills travel with it, and installing the plugin installs all of them — 107 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#delivery-suite 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.
- 29d ago Changed d16203ee7713
- 1mo ago First seen · 6 lines scan A 5dfe456f851d
delivery-suite is a plugin published in the GitHub repository levnikolaevich/claude-code-skills (577 stars, last pushed 3d 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-13.
Other plugins, from other repositories
github-workflow
Git commit, PR creation, review, and merge skills following Conventional Commits.
git
Git workflow automation (commit, PR, branching, changelog).
open-pr
Pre-flight checks and PR creation workflow: run tests, open a PR, code review, and check CI.
branch-recap
Tells you what your branch actually changed — what was done, why, and what deserves a second look, instead of the diff — then files the fixes into the commits they belong to.
aio-devops
GitHub, GitLab, and git worktree workflows in one toolkit — manage repos, PRs, MRs, pipelines, and parallel branches without juggling CLIs.
ooda-loop marketplace
Plugin marketplace listing 1 plugin: ooda-loop.