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 skills add avizmarlon/agent-skills --skill secure-secret-inputgit clone --depth 1 https://github.com/avizmarlon/agent-skillsWrote 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/avizmarlon/agent-skills/secure-secret-input)<a href="https://agentmods.dev/skills/avizmarlon/agent-skills/secure-secret-input"><img src="https://agentmods.dev/badge/skills/avizmarlon/agent-skills/secure-secret-input/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/avizmarlon/agent-skills/secure-secret-input"><img src="https://agentmods.dev/badge/skills/avizmarlon/agent-skills/secure-secret-input.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.00039 | $0.01706 |
| Opus 5.5 | $0.00016 | $0.00682 |
| Sonnet 5.5 | $0.00008 | $0.00341 |
| Haiku 4.5 | $0.00004 | $0.00171 |
Grade C, and why
secure-secret-input scanned grade C 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 2mo 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.
Harvests environment variableshighData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
### Pattern 1: Collect API Key for a Service How it starts
The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Secure Secret Input
Use this skill when an AI agent needs a user to provide any sensitive or private value such as API keys, tokens, cookies, session IDs, passwords, app IDs, client secrets, or recovery codes.
Rule
Never ask the user to paste a secret into chat. Instead, open a visible local terminal or secure prompt window with clear labeling.
Default flow:
-
Check first — does the value already exist in credential storage, environment variables, local configuration files, or an authenticated API? If yes, use it programmatically and do not ask the user.
-
If the user must provide it, open a visible local window or terminal with a clear title and purpose.
-
Mask input — use masked input when supported (e.g., PowerShell's
Read-Host -AsSecureStringon Windows, orread -sin bash on Unix). -
Write directly to destination — store the value directly to where it will be used:
- Project runtime:
.envfile (excluded from version control) - Long-lived credential: credential manager (1Password, Bitwarden, OS keychain, etc.)
- One-shot use: process-local memory only
- Application integration: native OS credential store
- Project runtime:
-
Print only safe metadata — after collection, output only:
- Status (success / failure)
- Destination path (e.g., env-var name, credential store item name)
- Boolean confirmation
Never print the actual value.
-
Clean up — delete temporary files, markers, or helper scripts that could contain the value.
-
Update documentation — record only the secret's logical name, purpose, and storage location in any inventory or documentation. Never record the value itself.
Window Text Example
When opening a local input window, make the purpose unambiguous. The user may see it out of context.
Title:
Secure Input - API_KEY_NAME
Body:
An AI assistant needs a sensitive value.
Label: API_KEY_NAME
Purpose: Authentication with service XYZ
Destination: Project .env and credential vault
Type or paste it here, not in the chat.
The value will not be printed or logged.
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.
- 2mo ago First seen · 160 lines · 39 tokens per session scan C 463611b7e2c3
secure-secret-input is a skill published in the GitHub repository avizmarlon/agent-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 1,706 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (harvests environment variables). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
duckduckgo-search
Free keyless web, news, and image search via ddgs.
mcporter
List, auth, and call MCP servers/tools from the terminal.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
safe-refactor
Restructure code while preserving behavior. Use for extraction, consolidation, ownership moves, or cleanup where verification must bracket structural edits.