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/nirecom/agents/create-keynpx skills add nirecom/agents --skill create-keygit clone --depth 1 https://github.com/nirecom/agentsWhat 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.00018 | $0.00441 |
| Opus 5 | $0.00009 | $0.00220 |
| Sonnet 5 | $0.00004 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
create-key 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 yesterday.
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
Generate a cryptographically random key or password for use in configuration.
Connection URL Passwords
When embedding a password in a connection URL (DATABASE_URL, REDIS_URL, AMQP URL, etc.),
the password component must be URL-safe. Standard base64 (+/=) breaks URL parsers
(real example: Prisma invalid port number).
Allowed formats:
hex(recommended — no special characters)- Linux/macOS:
openssl rand -hex 32 - PowerShell:
-join ((1..32)|%{'{0:x2}' -f (Get-Random -Max 256)})
- Linux/macOS:
base64url(no padding):openssl rand -base64 32 | tr '+/' '-_' | tr -d '='- Any string: percent-encode the password component before embedding in the URL
Prohibited: standard base64 (+/=) embedded unencoded in a URL password.
Variable separation (preferred): Provide both a composed URL and separate
POSTGRES_PASSWORD / POSTGRES_USER / POSTGRES_HOST variables — avoids URL escaping
issues entirely.
Opaque Secrets
For secrets not embedded in a URL (NextAuth secret, salt, JWT secret, etc.):
openssl rand -base64 32 or openssl rand -hex 32 — either is fine.
Handling and Storage
Once a secret appears in chat, it persists in conversation logs, screenshots, and terminal scrollback. To minimize exposure:
- User-side generation preferred — present the generation command; the user runs it.
- Secret manager preferred (1Password CLI, Docker secrets, age-sops, doppler, etc.).
- If Claude must present the value: development secrets only — never production.
- Remind the user to store the value in a password manager; warn that worktree deletion can silently destroy dotenv files containing the only copy.
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.
- yesterday First seen · 43 lines · 18 tokens per session scan A d2717eabdb3a
create-key is a skill published in the GitHub repository nirecom/agents (3 stars, last pushed 2d ago), licensed MIT. It adds 18 tokens to every session and 441 once invoked, about $0.0001 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…