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/dapi/claude-code-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/dapi/claude-code-marketplace/github-workflow)<a href="https://agentmods.dev/plugins/dapi/claude-code-marketplace/github-workflow"><img src="https://agentmods.dev/badge/plugins/dapi/claude-code-marketplace/github-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/dapi/claude-code-marketplace/github-workflow"><img src="https://agentmods.dev/badge/plugins/dapi/claude-code-marketplace/github-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
github-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 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": "github-workflow",
"description": "GitHub workflow: issues, PRs, worktrees, sub-issues",
"version": "2.11.3",
"author": {
"name": "Danil Pismenny",
"email": "[email protected]"
},
"homepage": "https://github.com/dapi/claude-code-marketplace",
"repository": "https://github.com/dapi/claude-code-marketplace",
"license": "MIT",
"keywords": ["github", "issues", "pull-request", "workflow", "worktrees", "sub-issues", "plan"]
}
What it installs
The manifest is a name and a version. 3 skills, 1 command travel with it, and installing the plugin installs all of them — 796 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.
- 1mo ago First seen · 14 lines scan A d1b7c53b8690
github-workflow is a plugin published in the GitHub repository dapi/claude-code-marketplace (16 stars, last pushed 1mo 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-08-30.
Other plugins, from other repositories
aidd-vcs
External artifacts: repo-init, commit, pull-request, release-tag, issue-create, resolve-conflict.
open-source
Collection of skills for open-source R and Python package developers.
magpie
Apache Magpie — a reusable, governance-agnostic framework of agentic skills for maintaining open-source projects: release management, security triage, PR and issue workflows, contributor growth, and repo health.
comfyui-plugin
ComfyUI custom-node pack lifecycle - scaffold a pack, create + seed the repo, open the gitops adoption PR, publish to the Comfy Registry, and add README screenshots.
registry-maintenance
Operator skills for maintaining the registry — ingest, backfills, overviews, release content, playbooks, coverage. Most need an admin API key.
project-shipper
PROACTIVELY use this agent when approaching launch milestones, release deadlines, or go-to-market activities. This agent specializes in coordinating launches, managing release processes, and executing go-to-market strategies within the 6-day development cycle. Should be triggered automatically when release dates are…