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/codeinfinity1/stram/secrets-handlingnpx skills add CodeInfinity1/Stram --skill secrets-handlinggit clone --depth 1 https://github.com/CodeInfinity1/StramWhat 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.00032 | $0.00420 |
| Opus 5 | $0.00016 | $0.00210 |
| Sonnet 5 | $0.00006 | $0.00084 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
secrets-handling 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
Secrets Handling
Purpose
Protect secrets in prompts, logs, files, screenshots, clipboard, shell commands, provider configs, and external messages.
When To Use
Use when reading env/config/logs, debugging providers, handling clipboard/screenshots, writing docs, sending messages, or integrating APIs.
Inputs And Evidence
- Secret-bearing source, redaction requirements, destination, and tool risk.
- Provider status or config output.
Tool Map
system_statusvoice_provider_statusread_fileos_clipboard_readscreen_capturesmessage-approval-policyagent_skill_script_catalogagent_skill_script_run
Native Scripts
scripts/redact_text.py: mechanically redacts likely tokens, private keys, and credential assignments from supplied text. This is a redaction helper, not semantic intent routing.
Workflow
- Identify likely secret-bearing sources.
- Minimize reading and copying.
- Redact values in responses and notes.
- Store secrets only in approved env/secret providers.
- Prevent external-visible sends with secrets.
- Report presence/missing rather than raw values.
Native Implementation Boundaries
- Use Stram redaction/status/policy tools.
- Do not import external secret scanners as implementation unless wrapped natively.
- Add scanners as Stram-owned tools if needed.
Safety And Approval
- Never print full tokens or private keys.
- Treat clipboard and screenshots as sensitive.
- Do not commit secrets.
Verification
- Check outputs are redacted.
- Confirm secret setup by presence flags, not values.
- Run dependency/security checks when relevant.
Failure Modes
- Echoing
.envvalues. - Sending logs with tokens to channels.
- Saving secrets in notes.
References
- Shortlist item:
secrets-handling.
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.
- yesterday First seen · 72 lines · 32 tokens per session scan A 34e738dacd80
secrets-handling is a skill published in the GitHub repository CodeInfinity1/Stram (10 stars, last pushed 22d ago), licensed MIT. It adds 32 tokens to every session and 420 once invoked, about $0.0002 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
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
golden-rss
Use when testing the rss golden build.
omh-code-review
This is a Hermes-native code-review workflow skill.
redteam-web-detail-pack
Routing and boundary guidance for authorized general web application security testing. Use as a web testing router when the attack surface should be dispatched to more specific web vulnerability skills.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
studio
Architecture Studio control plane — initialize or inspect a studio workspace, create and register projects, or route an architecture/AEC task to the right agent or skill. Use when the user runs /as:studio, asks to set up or open their studio, manage its projects, or describes a task without naming a skill.