essentials-claude-code

A collection of commands and agents that organize Claude Code tasks into plans, loops, swarms, and teams. Plans state when work is finished, and executors continue until tests pass.

In plain words
What is it for?
Use it to split work into dependent tasks, run several agents, track progress, save task state, and verify results with tests.
Why use it?
It reduces the risk of stopping with incomplete work or losing progress between tasks.

Plugin for Claude Code

Install

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.

Claude Code
/plugin marketplace add GantisStorm/essentials-claude-code
agentmods
npx agentmods add plugins/gantisstorm/essentials-claude-code/marketplace
Clone the repo
git clone --depth 1 https://github.com/GantisStorm/essentials-claude-code

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

essentials-claude-code 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 2d 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.

.claude-plugin/marketplace.json · 19 lines

What it actually says

{
  "name": "essentials-claude-code",
  "version": "3.43.0",
  "description": "Loops, swarms, and teams powered by Claude Code's built-in Task System. Plans define exit criteria. Executors run until tests pass. Done means actually done.",
  "author": "GantisStorm",
  "owner": {
    "name": "GantisStorm"
  },
  "homepage": "https://github.com/GantisStorm/essentials-claude-code",
  "plugins": [
    {
      "name": "essentials",
      "version": "3.43.0",
      "description": "24 commands, 8 agents. Loops, swarms, and teams powered by Claude Code's built-in Task System. Native task dependencies, ctrl+t progress, automatic persistence.",
      "source": "./essentials"
    }
  ]
}
Changes

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.

  1. 2d ago First seen · 19 lines scan A 281aa0c92814

Subscribe to this mod's changes

essentials-claude-code is a plugin published in the GitHub repository GantisStorm/essentials-claude-code (91 stars, last pushed 6mo ago), licensed Unlicense. 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.