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 skills/leefowlercu/agent-kit/op-secrets-creatornpx skills add leefowlercu/agent-kit --skill op-secrets-creatorgit clone --depth 1 https://github.com/leefowlercu/agent-kitWhat 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.00062 | $0.00928 |
| Opus 5 | $0.00031 | $0.00464 |
| Sonnet 5 | $0.00012 | $0.00186 |
| Haiku 4.5 | $0.00006 | $0.00093 |
Grade A, and why
op-secrets-creator 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
This skill enables agents to create secrets in 1Password using the op CLI. It supports creating Login, Password, API Credential, and Secure Note items with template support and vault selection.
The skill assumes the op CLI is installed and the user is already authenticated.
Table of Contents
Supported Item Types
| Type | Category | Use Case |
|---|---|---|
| Login | LOGIN | Website accounts, application logins |
| Password | PASSWORD | Standalone passwords, WiFi, PINs |
| API Credential | API_CREDENTIAL | API keys, access tokens, service credentials |
| Secure Note | SECURE_NOTE | Text notes, recovery codes, configurations |
Workflow
Phase 1: Context Assessment
Step 1: Understand the Request
Determine what the user wants to create:
-
Identify the item type:
- Login: Has username/password for a website or service
- Password: Standalone password without login context
- API Credential: API key, token, or service credential
- Secure Note: Text information to store securely
-
Gather required information:
- Title for the item (required)
- Target vault (optional, uses default if not specified)
- Field values based on item type
-
Check for special requirements:
- Should password be auto-generated?
- Are there tags to apply?
- Any custom sections needed?
See Item Templates Reference for field requirements per type.
Phase 2: Secret Creation
Step 2: Gather Field Values
Based on the item type, collect the necessary field values:
Login:
username: Account username or emailpassword: Account password (or use--generate-password)url: Website URL (via--urlflag)
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 126 lines · 62 tokens per session scan A 38ee728e5bae
op-secrets-creator is a skill published in the GitHub repository leefowlercu/agent-kit (6 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 928 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.