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/deepfusionlabs/deep-initWrote 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/commands/deepfusionlabs/deep-init/version)<a href="https://agentmods.dev/commands/deepfusionlabs/deep-init/version"><img src="https://agentmods.dev/badge/commands/deepfusionlabs/deep-init/version/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/commands/deepfusionlabs/deep-init/version"><img src="https://agentmods.dev/badge/commands/deepfusionlabs/deep-init/version.svg" alt="Reviewed on agentmods" width="80" 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.00037 | $0.00580 |
| Opus 5.5 | $0.00015 | $0.00232 |
| Sonnet 5.5 | $0.00007 | $0.00116 |
| Haiku 4.5 | $0.00004 | $0.00058 |
Grade A, and why
version 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 1mo 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
Report the running DeepInit version — fast, no analysis. Do exactly this, then stop:
-
State the loaded version verbatim. This line ships inside the plugin markdown that is actually loaded in your session, so it is the source of truth for "what is running right now":
DeepInit v0.7.2
-
Read the on-disk version (best-effort — skip gracefully if a path isn't present):
- a local clone of this repo →
.claude-plugin/plugin.json(the"version"field) - the marketplace-installed copy → the newest
plugin.jsonunder~/.claude/plugins/(the active pin is recorded in~/.claude/plugins/installed_plugins.json; a newer copy in the cache that the pin hasn't moved to means the update was fetched but not yet applied)
- a local clone of this repo →
-
Compare and advise:
-
loaded == on-disk → "You're running the latest version — you're all set."
-
loaded is behind on-disk → "The running plugin is STALE: a newer version is on disk but not live. Claude Code loads plugin markdown ONCE per session and does not re-read it mid-session, so one activation step remains — and it depends on your host. Detect your host first (from your system context), then do only the matching one:
- Plain terminal / CLI → run
/reload-plugins, or (more reliable for a version/command flip) start a new session. A reload picks up skills and hooks but doesn't rebuild the slash-command index, so this canary may not flip from/reload-pluginsalone — a new session is the sure path. - VS Code / JetBrains extension → restart the IDE itself (a full quit + reopen).
Developer: Reload Windowdoes not reload the plugin host, so the loaded number won't flip from a window reload (or a new chat in the same window). - Desktop app / web → fully restart the app (or reload the session) — a window reload alone is not enough.
Then run
/deep-init:versionagain to confirm the LOADED number flipped (it reports what's actually running, so it's the honest check that activation worked)." - Plain terminal / CLI → run
-
on-disk not found → just report the loaded version.
-
For a full active-vs-installed-vs-newest diagnosis across every plugin (and duplicate-shadow detection), run /oss-kit:oss-plugin-doctor.
$ARGUMENTS
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.
- 1mo ago First seen · 28 lines · 37 tokens per session scan A c11c543db66d
version is a command published in the GitHub repository deepfusionlabs/deep-init (6 stars, last pushed 23d ago), licensed MIT. It adds 37 tokens to every session and 580 once invoked, about $0.0001 per session on Opus 5.5. 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 commands, from other repositories
feedback
A design-stage security review for product requirement documents and other planning documents; a PRD is a document describing what a product should do.
compliance
A follow-up security check that verifies whether earlier findings were fixed and, depending on the selected mode, looks for new problems.
va
A read-only security review of a codebase across eight architecture areas, with findings checked against file-and-line evidence.
pentest
A read-only penetration-testing command for examining source code from an attacker’s perspective and producing proof-of-concept checks. Penetration testing is authorized security testing that tries to verify exploitable weaknesses.
redteam
A read-only review of infrastructure settings, infrastructure-as-code, and CI/CD pipelines using MITRE ATT&CK attack paths. MITRE ATT&CK is a catalogue of techniques attackers use, while CI/CD means the automated process that builds, tests, and deploys software.
run
A security-workflow coordinator that turns a natural-language request into a plan involving code review, verification, attack testing, or reporting.