Borrowing it
Nothing to install: this file belongs to Aviator-Coding/home-ops. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Aviator-Coding/home-ops/main/.agents/skills/secrets-1password/SKILL.mdgit clone --depth 1 https://github.com/Aviator-Coding/home-opsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/aviator-coding/home-ops/secrets-1password)<a href="https://agentmods.dev/skills/aviator-coding/home-ops/secrets-1password"><img src="https://agentmods.dev/badge/skills/aviator-coding/home-ops/secrets-1password/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/aviator-coding/home-ops/secrets-1password"><img src="https://agentmods.dev/badge/skills/aviator-coding/home-ops/secrets-1password.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00082 | $0.00831 |
| Opus 5.5 | $0.00033 | $0.00332 |
| Sonnet 5.5 | $0.00016 | $0.00166 |
| Haiku 4.5 | $0.00008 | $0.00083 |
Grade A, and why
secrets-1password 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 25d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Secrets: ExternalSecret, PushSecret and 1Password
Home-Lab and Homelab are different vaults. Mixing them is the usual
reason a new secret never arrives.
Tripwires
- Connect cannot see
Home-Lab. Vals (bootstrap and Talos) resolvesref+op://Home-Lab/...with theopCLI. In-cluster External Secrets uses 1Password Connect, which seesHomelab,Automation, andServicesonly. No ExternalSecret or PushSecret can read or writeHome-Lab. Machine-maintained items live in a Connect-visible vault. - A write that must land in one vault uses
onepassword-automation. The sharedonepasswordClusterSecretStore lists three vaults and picks by priority, so the target is not deterministic. The single-vault store is cluster-scoped on purpose: a namespaced SecretStore may only reference a Secret in its own namespace, and the Connect token lives insecurity. SecretSynced/Ready=Truedoes not mean non-empty. ESO writes a present-but-empty 1Password field as a zero-length string and reports healthy. On an auth failure, check the Secret key length (base64 -d | wc -c), not the ExternalSecret status.- Never seed a Secret with client-side
kubectl apply. The value is stored inkubectl.kubernetes.io/last-applied-configuration. Usekubectl create, or server-side apply, and do not print the value. - Connect token and service-account token are different credentials.
OP_SERVICE_ACCOUNT_TOKENis whatvalsuses forHome-Labon a workstation.OP_CONNECT_TOKENis a Connect access token, scoped to a whole vault (not an item) and used by CI against Connect. Do not reuse the cluster's ESO Connect token for CI. Skillauthentik-terraformfor the Automation-vault scope of the terraform-diff token. resources/is not a secret path. Renovate ignores it, and plaintext in git is forbidden. Bootstrap secrets stayref+op://Home-Lab/....
Where things live
| What | Path |
|---|---|
| App ExternalSecret | kubernetes/apps/base/<ns>/<app>/app/externalsecret.yaml |
| Shared store | ClusterSecretStore onepassword |
| Single-vault write store | kubernetes/apps/base/security/external-secrets/stores/onepassword/ (onepassword-automation) |
| Bootstrap injection | bootstrap/kustomize/apps/security/ via vals |
| Workstation token | OP_SERVICE_ACCOUNT_TOKEN in gitignored .secrets.env, vault Home-Lab |
| Postgres item recipe | recipes.md |
What ships with it
1 file 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.
- 25d ago First seen · 63 lines · 82 tokens per session scan A f8e04517aa10
secrets-1password is a skill published in the GitHub repository Aviator-Coding/home-ops (3 stars, last pushed today), licensed MIT. It adds 82 tokens to every session and 831 once invoked, about $0.0003 per session on Opus 5.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-09-29.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…