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/3awny/qshipWrote 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/3awny/qship/marketplace)<a href="https://agentmods.dev/plugins/3awny/qship/marketplace"><img src="https://agentmods.dev/badge/plugins/3awny/qship/marketplace/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/3awny/qship/marketplace"><img src="https://agentmods.dev/badge/plugins/3awny/qship/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
qship marketplace 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": "qship",
"description": "Open-source mirror of the qship pipeline — Jira ticket to production PR in one slash command. Hook-enforced, resumable, parallel/epic-mode capable, with optional Codex CLI integration for diversified model review.",
"owner": {
"name": "Ahmed Awny",
"email": "[email protected]"
},
"plugins": [
{
"name": "qship",
"description": "Bootstrapper for the qship pipeline. Installs a single configurator skill (/qship:configure) that walks you through ~25 questions about your codebase, then renders the 21-skill pipeline (plan / implement / TDD / review / E2E / PR) into your ~/.claude/skills/ tree. Hook-enforced, resumable, parallel/epic-mode capable. Works with both Claude Code and Codex CLI. Recommended companion plugins from anthropics/claude-plugins-official: superpowers, feature-dev, code-review, code-simplifier, pr-review-toolkit.",
"author": {
"name": "Ahmed Awny",
"email": "[email protected]",
"url": "https://github.com/3awny"
},
"category": "workflow",
"source": {
"source": "github",
"repo": "3awny/qship"
},
"homepage": "https://github.com/3awny/qship"
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json 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 · 26 lines scan A 29cb671b46a2
qship marketplace is a plugin published in the GitHub repository 3awny/qship (2 stars, last pushed 3mo 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-31.
Other plugins, from other repositories
open-source
Collection of skills for open-source R and Python package developers.
dark-factory
Curie's default dark factory agent: one labelled GitHub issue in, one reviewed pull request or one stated reason out. One agent reads the issue through the platform's getissue tool, pins acceptance criteria, plans, gets the plan reviewed by an Opus plan-reviewer subagent, writes a failing test where feasible, implemen.
github-activity
Read-only GitHub activity reporter for program managers. One hosted connector reads merged pull requests, opened and closed issues, and milestone movement across several repositories since a point in time. It holds no write tool, the tool policy allows only the read tool so anything else fails closed, and the…
fuse-rules
Global rules for all Claude Code sessions: APEX workflow, SOLID/DRY enforcement, project detection, agent delegation, frontend/git standards.
fullstack-dev-kit
Issue-to-PR workflow kit for any tech stack. Fetch a user story from your tracker (Jira, Linear, GitHub Issues, Azure DevOps) and any linked Figma designs, implement with plan approval, enforce >95% coverage and a security pass, generate e2e tests, open the PR, fix review findings, and move the ticket to review.
polisade
Polisade Orchestrator — autonomous development framework by Polisade. Claude operates as a full dev team: implement → test → PR → review → merge. (Technical id: polisade).