Outsider Stage 0.5
실제 봉인된 Outsider Stage 0.5 개입 체인을 재생하고 검증합니다
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기Keep secrets out of AI coding agents: agents see names, never values
저장소 README에서 가져옴
README 전체를 불러오는 중입니다. 아래는 저장된 발췌입니다.
Keep secrets out of your AI coding agent. It sees names, never values.
I kept handing secrets to my coding agent. Paste the API key into the prompt, or just say "read it from my .env".
It works — and now that key sits with the model provider, in the session log on disk, and in whatever output the agent prints next.
hivelock holds that message back before it's sent. The secret goes into a local encrypted vault, and you resend it by name:README 전문 보기 ↗I kept handing secrets to my coding agent. Paste the API key into the prompt, or just say "read it from my
.env".It works — and now that key sits with the model provider, in the session log on disk, and in whatever output the agent prints next.
hivelock holds that message back before it's sent. The secret goes into a local encrypted vault, and you resend it by name:
- STRIPE_SECRET_KEY=sk_live_…the real key you just pasted…
+ STRIPE_SECRET_KEY={{lock:STRIPE_SECRET_KEY}}
The agent only ever works with {{lock:STRIPE_SECRET_KEY}}. When it runs a command, hivelock fills in the real value at the last moment and masks it again in the output:
$ curl -H "Authorization: Bearer {{lock:GITHUB_TOKEN}}" api.github.com/user
[lock:GITHUB_TOKEN] ← what the agent gets back
curl -fsSL https://raw.githubusercontent.com/dip497/hivelock/main/install.sh | sh
Windows PowerShell or cmd:
powershell -NoProfile -ExecutionPolicy Bypass -Command "irm https://raw.githubusercontent.com/dip497/hivelock/main/install.ps1 | iex"
Picks the right binary for your machine, checks it, and asks which agents to protect. Or take one from Releases.
hivelock import .env # move the secrets you already have into the vault
hivelock doctor # check that it's working
hivelock # the manager: list, add, lock, stats
Then work as usual. hivelock help lists every command.
| Paste a secret in chat | held back before it's sent, and handed back to you as {{lock:NAME}} |
| Agent runs a command | real value injected at run time, masked in the output |
| Agent reads a file with secrets | masked before the model sees it, and locked away |
| Old sessions on disk | scrubbed in place |
hivelock lock NAME | human-only: passphrase, agents can't touch it |
hivelock ask NAME | the agent must ask you every single time |
Works with Claude Code · Codex · Copilot CLI · Gemini CLI · Cursor · Qwen Code on Linux, macOS and Windows.
It is not a sandbox. Read what it does and doesn't protect — then usage and agents.
MIT