Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add nicodiansk/turbocharge/plugin install 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/skills/nicodiansk/turbocharge/setup)<a href="https://agentmods.dev/skills/nicodiansk/turbocharge/setup"><img src="https://agentmods.dev/badge/skills/nicodiansk/turbocharge/setup.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00038 | $0.02018 |
| Opus 5 | $0.00019 | $0.01009 |
| Sonnet 5 | $0.00008 | $0.00404 |
| Haiku 4.5 | $0.00004 | $0.00202 |
Grade B, and why
setup scanned grade B with 1 finding 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 5d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Run `claude plugin list --json` to enumerate installed plugins and their enable state, then read `~/.claude/settings.json` `enabledPlugins`: How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Turbocharge
One-time audit and cleanup to make turbocharge your single orchestration system.
Announce: "Running turbocharge setup — auditing your config for conflicts."
The Goal
Turbocharge replaces ad-hoc agents, scattered skills, and custom commands with one pipeline. This setup finds and removes the overlap so Claude doesn't get confused about which system to use.
Audit Steps
1. Check for Competing Agents
Scan ~/.claude/agents/ for agent definitions that overlap with turbocharge agents:
| Turbocharge Agent | Conflicts With |
|---|---|
| builder | tdd-guide, implementer |
| planner | planner, architect |
| code-reviewer | code-reviewer |
| researcher | explorer, investigator |
| task-reviewer | spec-reviewer, quality-reviewer |
Also check for: session-wrapper, session-wrap, build-error-resolver (covered by turbocharge:debug)
Action: List conflicts and offer to delete them. Explain what turbocharge agent replaces each one.
2. Check for Duplicate Skills/Commands
Scan .claude/commands/ (project level) for commands that overlap with turbocharge skills:
| Turbocharge Skill | Conflicts With |
|---|---|
| wrap | session-wrap, wrap-up, session-wrapper |
| story | story-author, user-story, story-writer |
| plan | task-breakdown, plan-tasks, task-planner |
| review | code-review |
| build | implement, implement-story |
| brainstorm | brainstorm (if non-turbocharge) |
| debug | debug, troubleshoot |
Action: List conflicts with file paths. Offer to delete duplicates. Flag any that have unique functionality turbocharge doesn't cover (recommend keeping those).
3. Check agents.md Rule
Read ~/.claude/rules/common/agents.md (if exists):
- Does it reference turbocharge as the primary system? Good.
- Does it list phantom agents (agents not in
~/.claude/agents/)? Bad — offer to rewrite. - Does it reference both turbocharge AND other agent systems? Bad — offer to consolidate.
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.
- 5d ago First seen · 198 lines · 38 tokens per session scan B 6223ba3fa35d
setup is a skill published in the GitHub repository nicodiansk/turbocharge (2 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 2,018 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
weekly-digests
Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests"…
cloud-sync
Set up or check claude-mem cloud sync with cmem.ai Pro. Use when the user says "set up cloud sync", "sync my memories", "cmem pro", "cloud backup", "sync status", or wants their memory database backed up or synced to their cmem.ai account.
version-bump
Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. NPM publishing is the final human-required handoff because the maintainer…
fix-security-vulnerabilities-with-strix
Fix security vulnerabilities found by a Strix pentest (open-source CLI or app.strix.ai cloud) — triage by severity, patch the root cause rather than the symptom, and re-run Strix to prove each fix actually closes the exploit. Handles injection, XSS, SSRF, broken access control, IDOR, and other validated findings. Use…
ci-security-scanning-with-strix
Add security scanning to CI/CD with Strix — GitHub Actions, GitLab CI, or any pipeline — so every pull request gets a diff-scoped AI pentest that blocks vulnerable code before it merges, with results as PR comments and SARIF uploaded to code scanning. Covers both the self-hosted open-source CLI (runs in your runner)…
extract
Run the full Semantica semantic extraction pipeline on a file or selected text — NER, relations, events, coreference resolution, triplets, and validation. Clears result cache before each run. Returns Markdown tables with entity/relation/event/triplet results and inline validator warnings.