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/nicodiansk/turbochargeWrote 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/nicodiansk/turbocharge/marketplace)<a href="https://agentmods.dev/plugins/nicodiansk/turbocharge/marketplace"><img src="https://agentmods.dev/badge/plugins/nicodiansk/turbocharge/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/nicodiansk/turbocharge/marketplace"><img src="https://agentmods.dev/badge/plugins/nicodiansk/turbocharge/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
turbocharge 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 7d 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": "turbocharge",
"owner": {
"name": "Nicholas",
"email": "[email protected]"
},
"metadata": {
"description": "Engineering team orchestration plugins for Claude Code"
},
"renames": {
"turboflow": "turbocharge"
},
"plugins": [
{
"name": "turbocharge",
"source": {
"source": "url",
"url": "https://github.com/nicodiansk/turbocharge.git"
},
"description": "Engineering team orchestration for Claude Code. 10 skills, 6 agents, 2 hooks, 1 workflow — single pipeline from brainstorm to shipped code.",
"strict": true
}
]
}
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
2 files 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.
- 7d ago Changed 59bb60805c62
- 9d ago Changed 84c8b457fb33
- 10d ago Changed · +1 lines 7e5e545c6746
- 1mo ago First seen · 24 lines scan A 9a6ccc55f21f
turbocharge marketplace is a plugin published in the GitHub repository nicodiansk/turbocharge (3 stars, last pushed 4d 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
claude-mem-cursor
Persistent memory for Cursor. Hooks ingest tool use; MCP searches past sessions. Works with a local worker or a remote cmem.ai worker, and a local host-login observer or remote inference.
claude-mem-grok-bot
Persistent memory for Grok Bot. No host hooks: transcript watcher plus MCP. Local worker with host-login observer, or remote cmem.ai. Install without Cursor.
claude-mem-cowork
Claude-Mem for Cowork: captures tool use via hooks, streams fragments to cmem.ai (Pro runs the observer), and injects observations back into new sessions and spawned agents.
hivemind
Cloud-backed persistent memory powered by Deeplake — read, write, and share memory across Claude Code sessions and agents.
helper
Example domain plugin — a summarize-or-draft workflow the PM runs, the output format it follows, and a writing worker it can hand bulky material to. A minimal, runnable starting point for building your own plugins.
core
Engine-owned skills that ship with archie-hq itself rather than with a domain plugin: channel canvas, self-awareness, thread conduct, triggers and trigger-fired tasks.