safe info.
✳ SMALL PLUGINS. BIGGER PICTURE.

Let Claude cook.
Know what’s
on the stove.

More context for every command. More clarity about every change. Four focused plugins for developers who like to stay in the loop.

Explore the pluginsView marketplace
⌘ Built for your Claude Code workflow
claude / workspaceINTERACTIVE DEMO
❯ Check the pods across our environments.
⏺ Bashkubectl get pods --context prod-eu⚠ k8s: prod-eu
⏺ Bashkubectl get pods --context stagingk8s: staging
⏺ Bashaws s3 ls --profile sandboxaws: sandbox
[ context, made visible ]Illustrative session

The right environment should never be a guessing game.

CONTEXT AT EVERY STEP01 Know where02 Preview impact03 See the footprint04 Keep the learning
SEE IT IN ACTION

Less guessing.
In 18 seconds.

Watch env-badge put the target environment right under each command, with distinct colors for production, staging, and sandbox.

ENV-BADGE · ANIMATED WALKTHROUGH · NO AUDIO
Production targets appear in red with a warning marker; staging is yellow and sandbox is green. Animated example from the env-badge repository.
THE TOOLKIT

Four plugins.
A little less guesswork.

Use the one you need.
Bring them together when you want
the whole picture.

ENVIRONMENT AWARENESS01

claude-env-badge

Right command. Right environment.

$ kubectl get pods --context prod-eu⚠ k8s: prod-eu
ProductionStagingSandbox

AWS profiles and Kubernetes contexts, right under the Bash command. Color-coded so production catches your eye.

Explore env-badge ↗
IMPACT PREVIEW02

claude-blast-radius

Before “allow,” see what’s at stake.

$ rm -rf ./build
1,204files48 MBsize1,117not in git

Measure deletion impact at the permission prompt. Add your own dry-run rules for the commands you work with.

Explore blast-radius ↗
ACTION VISIBILITY03

claude-footprint

Know what your agent touched.

CHANGED1
└ prod-eks / web  └ deployment api · rollout restart
LOOKED AT24 calls

A live map of parsed AWS, Kubernetes, and supported MCP activity. See scope, action class, and reported outcomes in one pane.

Explore footprint ↗Repository access required
PERSISTENT MEMORY04

2brain

Your next session starts wiser.

SESSION TAKEAWAYS
Capture·Compile·Recall
knowledge that survives /clear

Turn session lessons into a plain-text wiki. Recall relevant knowledge in future sessions across Claude Code and Codex.

Explore 2brain ↗Repository access required
A LITTLE PHILOSOPHY

Powerful agents.
Informed humans.

01 /

Put context where decisions happen.

An environment under a command. An impact preview at approval. An action map beside your work.

02 /

Keep the boundaries clear.

env-badge, blast-radius, and footprint provide visibility. They don’t allow or block commands, and their parsers have limits. A missing indicator doesn’t mean an action is safe.

03 /

Make what you learn yours.

2brain stores knowledge in Markdown and JSONL in a Git repository. Read it, inspect it, and carry it into your next session.

MAKE YOURSELF AT HOME

Small addition.
Clearer workflow.

Pick a plugin and add it to Claude Code.
Your terminal. A little more informed.

Read the marketplace guide ↗
/plugin marketplace add aqaurius6666/claude-marketplace
/plugin install env-badge@aqaurius6666

Enable function hooks with CLAUDE_CODE_ENABLE_FUNCTION_HOOKS=1 when starting Claude Code. See the plugin’s README for Desktop setup.

A few things to know.

Do I need all four plugins?

No. Each plugin has its own repository and can be installed independently. Start with the gap in your workflow that matters most.

Do these plugins prevent dangerous commands?

No. env-badge, blast-radius, and footprint are display tools, not security gates. Keep using Claude Code’s permission controls. The parsers cannot see every action inside scripts, wrappers, or other tools.

What do I need to get started?

The three display plugins use Claude Code function hooks. Enable them as described in each README. footprint and 2brain require repository access. For 2brain, follow its installer guide to set up the knowledge directory and optional maintenance jobs.