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 commands/i4ctime/q-ring/qring-exec-safegit clone --depth 1 https://github.com/I4cTime/q-ringWrote 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/commands/i4ctime/q-ring/qring-exec-safe)<a href="https://agentmods.dev/commands/i4ctime/q-ring/qring-exec-safe"><img src="https://agentmods.dev/badge/commands/i4ctime/q-ring/qring-exec-safe.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.00017 | $0.00256 |
| Opus 5 | $0.00009 | $0.00128 |
| Sonnet 5 | $0.00003 | $0.00051 |
| Haiku 4.5 | $0.00002 | $0.00026 |
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 3d 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.
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.
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.
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.
- 3d ago First seen · 24 lines · 17 tokens per session scan A 1e89f5d130af
qring-exec-safe is a command published in the GitHub repository I4cTime/q-ring (4 stars, last pushed 3d ago), licensed AGPL-3.0. It adds 17 tokens to every session and 256 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 commands, from other repositories
refactor
Refactor existing artifacts to close drift from canonical contracts. The two modes target different artifact classes and use different agents.
upgrade
Bring this project's AIDE methodology artifacts up to date with canonical by calling aideupgrade and walking the user through each drifted category interactively.
xpoz-best-practices
Reference docs for Xpoz query syntax, pagination, field selection, platform tools, and authentication. Usage: /xpoz-best-practices.
xpoz-track
Manage tracked keywords, users, subreddits, and hashtags across Twitter, Instagram, Reddit, and TikTok. Usage: /xpoz-track.
xpoz-setup
Configure the Xpoz MCP connection and verify your account. Usage: /xpoz-setup.
align
Verify spec-vs-spec alignment and brevity across the intent tree. This is NOT QA — QA checks code against a spec; alignment checks whether specs are consistent with their ancestors and internally tight against the Brevity Contract. The aligner runs three passes per walk.