secrets
by crockalet · ★ 1 · updated today
Hand Claude an API token without it reading the value: you type it into a field above the prompt, Claude uses it in Bash as $NAME, and it is redacted from every tool result.
Install
/plugin marketplace add crockalet/claude-mods/plugin install secrets@claude-modsThen run /reload-plugins or start a new session. Requires Claude Code 2.1.287+.
What it hooks into
From an automated scan with claude plugin validate, not a security review. Mods run with your permissions; read the code before installing.
- Events
session.startsession.endprompt.composeagent.spawnprompt.editsession.appendprompt.submittool.callturn.completetool.checkcommand.runui.render- API calls
$.clock.now$.command.register$.process.run$.state.get$.state.set$.tool.register$.ui.resolve$.ui.toast- Draws
AbovePrompt- Can see
subagent spawnsevery promptmcp__secrets__request_secret callsevery tool call- Reach
- level 2 of 3 other: $.state.getother: $.state.setruns processesdrives Claudedraws
Origin
- How it got here
- Automated scan of public GitHub repos, via the CC0 dataset awesome-claude-code-mods (scan of ).
- Repository
- github.com/crockalet/claude-mods
- Path in repo
plugins/secrets- Source commit
8108ec5the exact code the scan read- Author
- @crockalet
- License
- No license declared — ask the author before reusing code.
- First published
- Last pushed
- First listed here
Name and description come from the mod's own manifest. We link to the code; we don't host it, and it stays under its author's license.
More from crockalet/claude-mods
breadcrumbs
crockalet/claude-mods
A pane beside the session that Claude talks to you through: the task, what it is doing, the notes it files, the questions it went on without, and manual tests you run when you get to them.
breadcrumbs-launcher
crockalet/claude-mods
Starts breadcrumbs' manual-test testers the moment you press Start, without going through the main agent.