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-deleternpx skills add leefowlercu/agent-kit --skill op-secrets-deletergit 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.00057 | $0.00783 |
| Opus 5 | $0.00028 | $0.00392 |
| Sonnet 5 | $0.00011 | $0.00157 |
| Haiku 4.5 | $0.00006 | $0.00078 |
Grade A, and why
op-secrets-deleter 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
This skill enables agents to delete or archive secrets in 1Password using the op CLI. It supports permanent deletion for items no longer needed and archiving for items that might need to be recovered later.
The skill assumes the op CLI is installed and the user is already authenticated.
Table of Contents
Supported Operations
| Operation | Use Case |
|---|---|
| Delete Item | Permanently remove an item from 1Password |
| Archive Item | Move an item to Archive for potential recovery |
Workflow
Phase 1: Context Assessment
Step 1: Understand the Request
Determine what the user wants to delete or archive:
-
Identify the target item:
- Item name or ID
- Vault location (if known or ambiguous)
-
Identify the operation type:
- Permanent deletion (item removed completely)
- Archive (item moved to Archive, recoverable)
-
Assess the situation:
- Is the credential compromised? (permanent delete recommended)
- Might the item be needed later? (archive recommended)
- Is this a cleanup of test/duplicate items? (permanent delete)
-
Clarify if needed:
- If item name is ambiguous, ask for vault or use item ID
- If operation type is unclear, recommend archive as safer option
Phase 2: Delete Execution
Step 2: Confirm Deletion
Before executing a destructive operation, confirm with the user:
-
For permanent deletion:
- Warn that this action cannot be undone
- Confirm the correct item is targeted
- Suggest archive as alternative if appropriate
-
For archiving:
- Confirm the item will be moved to Archive
- Explain that archived items can be restored via 1Password app
What ships with it
3 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 · 109 lines · 57 tokens per session scan A f8ae69d68067
op-secrets-deleter is a skill published in the GitHub repository leefowlercu/agent-kit (6 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 783 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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…