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 andisab/swe-marketplacenpx agentmods add plugins/andisab/swe-marketplace/archgit clone --depth 1 https://github.com/andisab/swe-marketplaceGrade A, and why
arch 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 3d 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": "arch",
"description": "Architecture and build orchestration agents for system design, multi-agent coordination, and context management.",
"version": "1.0.0",
"author": {
"name": "Andis A. Blukis",
"email": "[email protected]",
"url": "https://github.com/andisab"
},
"homepage": "https://github.com/andisab/swe-marketplace",
"repository": "https://github.com/andisab/swe-marketplace",
"license": "MIT",
"keywords": [
"architecture",
"orchestration",
"system-design",
"coordination",
"planning"
],
"agents": [
"./agents/arch-context-agent.md",
"./agents/build-orchestrator.md"
]
}
What it installs
The manifest is a name and a version. 2 agents travel with it, and installing the plugin installs all of them — 784 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.
- 3d ago First seen · 25 lines scan A 7b0f0401987f
arch is a plugin published in the GitHub repository andisab/swe-marketplace (21 stars, last pushed 15d 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
skillsforge-marketplace
Plugin marketplace listing 31 plugins: agent-team-builder, ai-summary-request, apify-js-sdk, article-title-optimizer, cronjob-org.
ds-continuity
Death & Sourdough series continuity checker. MANDATORY before writing or editing ANY prose chapter for the Death & Sourdough project.
claude-ops
Claude Code operations toolkit. Twelve skills: audit-skill-visibility (audit whether each installed skill is actually VISIBLE to the model, and diagnose why most of a fleet never gets used — a skill is invisible when its description is dropped by Claude Code's skill-listing context budget, which sheds descriptions…
computer-use
Operating knowledge for Claude Code's built-in computer-use MCP server — the desktop screen-control surface. /computer-use:diagnose resolves a symptom to a cause instead of retrying: why every screenshot is downscaled to a fixed pixel budget and why zoom (not a bigger display) is the way back to detail, how to read a.
coupling
Iteratively reduces coupling in any repository at any altitude — documents, code modules, applications, or repositories: scans for change-transmitting dependencies typed against a coupling model (strength ladder, connascence, volatility weighting), verifies every finding, applies a budgeted batch of safe…
godot-devtool
Claude Code skills and an IDE-style Agent for Godot Engine development through the godot-devtool MCP server.