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.
/plugin marketplace add HermeticOrmus/claude-code-game-developmentnpx agentmods add plugins/hermeticormus/claude-code-game-development/backend-developmentgit clone --depth 1 https://github.com/HermeticOrmus/claude-code-game-developmentWrote 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/hermeticormus/claude-code-game-development/backend-development)<a href="https://agentmods.dev/plugins/hermeticormus/claude-code-game-development/backend-development"><img src="https://agentmods.dev/badge/plugins/hermeticormus/claude-code-game-development/backend-development.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
backend-development 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 yesterday.
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": "backend-development",
"source": "./plugins/backend-development",
"description": "Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development",
"version": "1.2.3",
"author": {
"name": "Seth Hobson",
"url": "https://github.com/wshobson"
},
"homepage": "https://github.com/wshobson/agents",
"repository": "https://github.com/wshobson/agents",
"license": "MIT",
"keywords": [
"backend",
"api-design",
"graphql",
"tdd",
"architecture",
"temporal",
"workflow-orchestration",
"distributed-systems"
],
"category": "development",
"strict": false,
"commands": [
"./commands/feature-development.md"
],
"agents": [
"./agents/backend-architect.md",
"./agents/graphql-architect.md",
"./agents/tdd-orchestrator.md",
"./agents/temporal-python-pro.md"
],
"skills": [
"./skills/api-design-principles",
"./skills/architecture-patterns",
"./skills/microservices-patterns",
"./skills/workflow-orchestration-patterns",
"./skills/temporal-python-testing"
]
}What it installs
The manifest is a name and a version. 5 skills travel with it, and installing the plugin installs all of them — 216 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#backend-development 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.
- yesterday First seen · 41 lines scan A e95cf91fdc8f
backend-development is a plugin published in the GitHub repository HermeticOrmus/claude-code-game-development (59 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-09-03.
Other plugins, from other repositories
mutation-testing
Measures whether a test suite can actually detect faults, not merely execute code: /mutation-testing:principles answers operator, mutant-state, and metric questions from the primary literature; /mutation-testing:setup verifies the ecosystem's mutation tool and writes the tracked config; /mutation-testing:audit ru.
implementation
Disciplined implementation stage: execute approved plans inline (/implementation:implement) or via orchestrated worker subagents (/implementation:implement-dispatch) with incremental validation, TDD-by-default cadence, green-checkpoint commits, scope-fence drift detection, and divergence detection that routes back.
debugging
Debug observed failures via a disciplined six-phase loop: build a fast deterministic reproduction signal, reproduce, rank falsifiable hypotheses, instrument, fix with a regression test, then clean up and post-mortem.
backend-development
Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development.
f5-framework
F5 Framework - AI-powered development framework with quality gates, TDD support, and enterprise-grade tooling for Claude Code.
workflow-skills
Issue triage, TDD, CI fix-with-memory, design-system guard, PR review, dead-code and doc-rot cleanup, comment and test reaping, code-health and visual-QA audits, evidence-checked claims, worktree setup, project bootstrap, cross-provider skill parity, and session wrap-up skills.