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/lttr/claude-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/lttr/claude-marketplace/maintenance)<a href="https://agentmods.dev/plugins/lttr/claude-marketplace/maintenance"><img src="https://agentmods.dev/badge/plugins/lttr/claude-marketplace/maintenance/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/lttr/claude-marketplace/maintenance"><img src="https://agentmods.dev/badge/plugins/lttr/claude-marketplace/maintenance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
maintenance 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 8d 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": "maintenance",
"description": "Repository upkeep skills: docs-checker (audit context files for broken references and stale content) and dependency-update (one reviewable dependency PR per run, with a deterministic scan script)",
"version": "0.1.1",
"author": {
"name": "Lukas Trumm"
},
"keywords": [
"maintenance",
"dependencies",
"upgrade",
"docs",
"audit",
"pnpm",
"npm"
]
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 186 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.
- 8d ago Changed 422a44483513
- 21d ago First seen · 18 lines scan A e6dff0af54ca
maintenance is a plugin published in the GitHub repository lttr/claude-marketplace (2 stars, last pushed 7d 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-23.
Other plugins, from other repositories
ados marketplace
Agentic Delivery OS - AI-powered software delivery system with 10-phase workflow.
construction-pm
Create project estimates, change orders, progress reports, and RFI responses for construction project management.
pf-workflow
Spec-driven workflow toolkit for multi-agent CLI development: task packets, journal, retro, autopilot.
weft
Deterministic workflow tracking with event-sourced logs for Claude Code.
divisible-work
Coordinates verified work using GPT-6.1 Sol or GPT-6 Luna, preferring permitted same-project Codex chats with native subagents as a portable fallback.
cadence
A project workflow plugin called cadence that records decisions, limits, unresolved questions, and next steps during discussions. It also supports handing work from one coding session to another.