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.
npx agentmods add commands/daypunk/lockedin/setupgit clone --depth 1 https://github.com/daypunk/LockedInWhat 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 | $0.00100 | $0.02782 |
| Opus 5 | $0.00050 | $0.01391 |
| Sonnet 5 | $0.00020 | $0.00556 |
| Haiku 4.5 | $0.00010 | $0.00278 |
Grade B, and why
setup scanned grade B with 2 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 yesterday.
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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
`${CLAUDE_CONFIG_DIR:-$HOME/.claude}/lockedin/hud.py` (chmod 0755). Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
# Attempt 2 — curl GitHub API How it starts
The opening of the file, as written. The whole thing — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/lockedin:setup — wizard
Run after /plugin install lockedin@lockedin, or any time you want to
reconfigure. Each step is independent and reversible.
Where state lives
- LockedIn runtime config:
${CLAUDE_CONFIG_DIR:-$HOME/.claude}/lockedin/config.json - HUD script:
${CLAUDE_CONFIG_DIR:-$HOME/.claude}/lockedin/hud.py - Backup of any previous statusLine:
${CLAUDE_CONFIG_DIR:-$HOME/.claude}/lockedin/.previous-statusline.json - Claude Code settings:
${CLAUDE_CONFIG_DIR:-$HOME/.claude}/settings.json
If the lockedin Python CLI is on PATH, prefer it for file mutations
(it has the safe-write logic already); otherwise perform the equivalent
operations directly with Read / Write tools.
Boot check
Perform this section first, before anything else.
1. Read existing config
Run:
CONFIG_FILE="${CLAUDE_CONFIG_DIR:-$HOME/.claude}/lockedin/config.json"
cat "$CONFIG_FILE" 2>/dev/null || echo "__MISSING__"
Parse the result:
- If the output is
__MISSING__or the file does not contain asetup_completedkey, setalready_configured=false. - Otherwise set
already_configured=trueand note the storedsetup_versionvalue (may be absent in older configs).
2. Detect installed plugin version
Run:
python3 -c "from lockedin import __version__; print(__version__)" 2>/dev/null \
|| cat "${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json" 2>/dev/null \
| python3 -c "import sys,json; d=json.load(sys.stdin); print(d.get('version','unknown'))" 2>/dev/null \
|| echo "unknown"
Capture the first successful output as current_version. If all
commands fail, set current_version="unknown" and continue.
3. Fetch latest available version (best-effort, fail gracefully)
Try each fallback in order. Stop at the first success. If every
attempt fails, set latest_version="unknown" and continue silently —
never crash or block on this step.
# Attempt 1 — gh CLI
gh api repos/daypunk/LockedIn/releases/latest --jq .tag_name 2>/dev/null
# Attempt 2 — curl GitHub API
curl -sf https://api.github.com/repos/daypunk/LockedIn/releases/latest \
| python3 -c "import sys,json; print(json.load(sys.stdin).get('tag_name',''))" 2>/dev/null
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.
- yesterday First seen · 339 lines · 100 tokens per session scan B 57d646819583
setup is a command published in the GitHub repository daypunk/LockedIn (127 stars, last pushed 3mo ago), licensed MIT. It adds 100 tokens to every session and 2,782 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
apply
You are orchestrating a two-agent job application workflow. The job posting is provided below as $ARGUMENTS (either a URL or pasted text).
setup
You are running the onboarding setup for the AI Job Search framework. Your goal is to collect the user's professional information and populate all profile files so the /apply workflow works out of the box.
outcome
You are recording what happened to a job application: progress updates (interview invitations, stages completed, offers) and final resolutions (hired, rejected, no response). The data lands in two places the framework already reads but nothing systematically writes.
add-portal
You are helping the user build a job-portal search skill for a job board in their market. The repo ships worked examples of the pattern (four Danish portals plus the country-agnostic linkedin-search and freehire-search), and the README invites users elsewhere to build equivalents — this command turns that invitation…
add-template
You are helping the user register their own CV or cover letter template with the AI Job Search framework — LaTeX, Typst, or any other toolchain that compiles to PDF from the command line. The framework ships with moderncv (banking style) for CVs and a custom cover.cls for cover letters. This command lets the user swap…
gmail-sync
You are scanning the user's Gmail for status signals on tracked job applications (interview invites, assessment links, offers, rejections) and, once approved, writing the detected changes into jobsearchtracker.csv and documents/applications/ /outcome.md - the same two places /outcome writes to, in the same schema.