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/me2resh/apexyardWrote 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/me2resh/apexyard/marketplace)<a href="https://agentmods.dev/plugins/me2resh/apexyard/marketplace"><img src="https://agentmods.dev/badge/plugins/me2resh/apexyard/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/me2resh/apexyard/marketplace"><img src="https://agentmods.dev/badge/plugins/me2resh/apexyard/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
apexyard 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 2d 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": "apexyard",
"description": "ApexYard plugins: ORBIT planning and fork-only add-ons for an ApexYard ops fork.",
"owner": {
"name": "me2resh",
"url": "https://github.com/me2resh"
},
"plugins": [
{
"name": "orbit",
"source": {
"source": "github",
"repo": "me2resh/orbit-spec"
},
"description": "ORBIT planning lifecycle: plan, snapshot, reconcile, slice, progress"
},
{
"name": "apexyard-status",
"source": "./plugins/apexyard-status",
"description": "Fork-only, display-only status band above the prompt: active ticket, PRs waiting for /approve-merge, reviewer lock"
},
{
"name": "apexyard-explainer",
"source": "./plugins/apexyard-explainer",
"description": "Display-only pane that explains each tool call in one plain sentence"
},
{
"name": "apexyard-bootcamp",
"source": "./plugins/apexyard-bootcamp",
"description": "Display-only guided bootcamp pane with nine modules and session checkpoints"
}
]
}
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.
- 2d ago First seen · 34 lines scan A d0ab9d59be90
apexyard marketplace is a plugin published in the GitHub repository me2resh/apexyard (532 stars, last pushed today), 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-10-16.
Other plugins, from other repositories
before-you-build
Pre-build product risk review for founders, product teams, and AI-assisted builders before implementation starts.
obw
Obsidian Workspace — project-scoped vault productivity (capture / notes / PM). Skills own folder layout and templates; /obw:pm splits a spec into blocking tickets; /issue is a Claude Mod pane that lists a view of the project's dashboard, draws Mermaid as text diagrams, and can open a card in the browser through viz.…
feature-to-pr-factory
Turn one feature into dependency-ordered GitHub or GitLab issues, then build each ticket into its own reviewed, tested PR or MR with agents.
mission-control
SDLC management for Operations, Asgard, and CAMPPS: prepared issue drafts, live schema sync, board schemas, labels, project fields, metrics, and card validation.
feishu-calendar
Manage Feishu (Lark) calendar events — create, read, update, delete events and manage attendees via the Feishu Open Platform Calendar API v4.
gse
GSE-One — AI engineering companion for structured SDLC management. 24 commands, adaptive risk analysis, unified backlog, knowledge transfer, worktree isolation.