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/spotify/confidence-ai-plugins/migrate-optimizely-execute-accessgit clone --depth 1 https://github.com/spotify/confidence-ai-pluginsWhat 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.00056 | $0.00517 |
| Opus 5 | $0.00028 | $0.00259 |
| Sonnet 5 | $0.00011 | $0.00103 |
| Haiku 4.5 | $0.00006 | $0.00052 |
Grade A, and why
migrate-optimizely-execute-access 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 3d 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.
What it actually says
Treat this slash command as /migrate-optimizely execute access.
First: Confidence auth (check, then ask only if needed)
Read skills/migrate-optimizely/SKILL.md and
skills/migrate-optimizely/access.md (agent-only; do not narrate).
Do not ask them to sign in if you already know they are authenticated. Prove it first (same turn, before any user-facing login ask):
$TMPDIR/confidence_tokenexists, JWTexpis in the future, andGET /v1/usersreturns 200 with at least the operator user.- Or a session token you already captured this chat (Debug clipboard / prior execute) still passes that smoke-test.
If authenticated: say you are using their Confidence account (email / workspace from the smoke-test). Do not ask them to log in. Do not open the browser. Continue execute access (consent gate, then writes).
If not authenticated (missing, expired, 401/403, or no token): ASK them to sign in to their Confidence account. Do not open the browser until they agree. Use a structured question:
Starting Phase 0 — Access execute. You are not signed in to Confidence. I need your account to create groups and send invites.
- Sign in now — open Confidence login in the browser
- Debug token — I’ll copy from Confidence Debug after you say “copied”
⏸ awaiting user until they pick. Then follow hard gate §2 in
access.md (auth.py login, or Option B). Never paste a token
prompt first. Never echo the token.
Then follow execute access in access.md. Require a completed
access plan (optimizely-access-migration-*.md, Generation Status
complete, ticked consent rows). If the plan is missing, run
/migrate-optimizely-plan-access first — do not invite from memory.
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.
- 3d ago First seen · 50 lines · 56 tokens per session scan A 2fcf7472d0be
migrate-optimizely-execute-access is a command published in the GitHub repository spotify/confidence-ai-plugins (8 stars, last pushed yesterday), licensed Apache-2.0. It adds 56 tokens to every session and 517 once invoked, about $0.0003 per session on Opus 5. 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.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.