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/urmzd/dotfiles/manage-secretsnpx skills add urmzd/dotfiles --skill manage-secretsgit clone --depth 1 https://github.com/urmzd/dotfilesWrote 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/urmzd/dotfiles/manage-secrets)<a href="https://agentmods.dev/skills/urmzd/dotfiles/manage-secrets"><img src="https://agentmods.dev/badge/skills/urmzd/dotfiles/manage-secrets.svg" alt="Measured on agentmods" 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 | $0.00048 | $0.01756 |
| Opus 5 | $0.00024 | $0.00878 |
| Sonnet 5 | $0.00010 | $0.00351 |
| Haiku 4.5 | $0.00005 | $0.00176 |
Grade B, and why
manage-secrets scanned grade B with 1 finding 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 5d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
chmod 600 config.yaml How it starts
The opening of the file, as written. The whole thing — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Secrets with 1Password
Philosophy
Secrets never sit in plaintext in the repo, in shell history, or in long-lived
shell env. 1Password is the only source of truth. Files commit references
(op://vault/item/field); resolution happens at command time, in the child
process only, via op run or op inject. Scanning and leak response stay in
[[audit-security]]; this skill owns the storage and injection workflow.
Prerequisites
op --version # CLI present (installed via Brewfile: cask "1password-cli")
op whoami # signed in; if not: `op signin` (or unlock via the 1Password desktop app)
op vault list # confirm the target vault exists
The 1Password desktop app unlocks biometric integration and enables the op
shell plugins (op plugin init aws|gh|...). For headless / CI, use a service
account token instead (see CI section).
The reference format
op://<vault>/<item>/[<section>/]<field>
Examples: op://Dev/aws/access_key_id, op://Dev/snowflake/credentials/password.
Vaults and items can be addressed by name or UUID; UUIDs survive renames and
are preferred in committed files for projects with churn.
Store a secret
For ad-hoc storage, prefer creating a typed item over stashing things in a Secure Note (typed items get the right field names, masking, and shell-plugin support):
# API token / opaque credential
op item create --vault Dev --category "API Credential" --title myservice \
credential="$(pbpaste)" # never type the value on the command line
# Login (username + password + URL)
op item create --vault Dev --category login --title github-bot \
username=ci-bot password=- url=https://github.com # `=-` reads value from stdin
# Add or update a field on an existing item
op item edit myservice --vault Dev "credential[concealed]=$(pbpaste)"
After creation, get the reference (do not echo the value):
op item get myservice --vault Dev --format json | jq -r '.fields[] | "\(.label) -> op://Dev/myservice/\(.id)"'
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.
- 5d ago First seen · 183 lines · 48 tokens per session scan B 8120dd1a497d
manage-secrets is a skill published in the GitHub repository urmzd/dotfiles (3 stars, last pushed 23d ago), licensed Apache-2.0. It adds 48 tokens to every session and 1,756 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
benchling-integration
Benchling Python SDK and REST API integration for registry entities, inventory, ELN entries, workflows, Benchling Apps, and Data Warehouse queries. Use when automating lab data with benchling-sdk or the v2 API.
astropy
Core Python library for astronomy and astrophysics workflows that need Astropy APIs, including units/quantities, coordinates, FITS I/O, tables, time systems, WCS, and cosmology. Use when implementing or debugging astronomical data analysis code with Astropy.
esm
Comprehensive toolkit for EvolutionaryScale protein language models including ESM3 (generative multimodal design across sequence, structure, and function) and ESM C (efficient embeddings). Use for protein sequence/structure/function tasks, inverse folding, embeddings, variant design, and ESMFold2 structure prediction…
ralph-loop
Ralph Wiggum 迭代开发循环。三阶段工作流（需求→规划→构建），每阶段有 code review + 测试 gate。 触发词：ralph loop、迭代开发、interview me、plan system、build system。.
create-pr
Rebase from the latest origin/main, squash the commits from it, and then create a PR on github with intelligent commit messages based on staged changes.
mcp-notion-usage-guide
MCP Notion工具使用指南，包含常见问题解决方案和最佳实践。使用当： (1) 访问Notion数据库view URL出现"URL type view not currently supported"错误， (2) 需要获取数据库schema和表结构信息， (3) 查询数据库中的条目内容， (4) 创建页面时MULTISELECT字段值不存在导致失败， (5) 需要更新数据库schema添加新选项， (6) 开发需要集成Notion数据的自动化工作流， (7) querydatasources/query-database-view返回Business Plan要求错误， (8) 需要在无Business…