qring:exec-safe

A command for running shell commands with secrets from q-ring added as environment values and sensitive output redacted.

In plain words
What is it for?
Running builds, tests, and development tools that need environment variables stored in q-ring.
Why use it?
It avoids placing credentials directly in commands or source files and helps prevent them appearing in logs.

Command

Install

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.

agentmods
npx agentmods add commands/i4ctime/q-ring/exec-safe
Clone the repo
git clone --depth 1 https://github.com/I4cTime/q-ring
Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 138 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00038 $0.00138
Opus 5 $0.00019 $0.00069
Sonnet 5 $0.00008 $0.00028
Haiku 4.5 $0.00004 $0.00014

Measured yesterday against content hash 9ad129a1f667, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

qring:exec-safe 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.

cursor-plugin/commands/exec-safe.md · 13 lines

The source is not reproduced here

Licensed AGPL-3.0

The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

Changes

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.

  1. yesterday First seen · 13 lines · 38 tokens per session scan A 9ad129a1f667

Subscribe to this mod's changes

qring:exec-safe is a command published in the GitHub repository I4cTime/q-ring (4 stars, last pushed yesterday), licensed AGPL-3.0. It adds 38 tokens to every session and 138 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.