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/bicced/end-of-turn-queue/cleargit clone --depth 1 https://github.com/bicced/end-of-turn-queueWrote 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/bicced/end-of-turn-queue/clear)<a href="https://agentmods.dev/commands/bicced/end-of-turn-queue/clear"><img src="https://agentmods.dev/badge/commands/bicced/end-of-turn-queue/clear.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.00010 | $0.00148 |
| Opus 5 | $0.00005 | $0.00074 |
| Sonnet 5 | $0.00002 | $0.00030 |
| Haiku 4.5 | $0.00001 | $0.00015 |
Grade A, and why
clear 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 4d 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.
What it actually says
!Q="${CLAUDE_PROJECT_DIR}/.claude/prompt-queue"; if [ -s "$Q" ]; then n="$(grep -c '[^[:space:]]' "$Q" 2>/dev/null || true)"; [ -n "$n" ] || n=0; : > "$Q"; echo "Cleared $n queued prompt(s)."; else echo "Queue already empty."; fi
Reflect the command output above in one short line — it will say either how many prompts were cleared or that the queue was already empty. Take no further action.
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.
- 4d ago First seen · 9 lines · 10 tokens per session scan A 8123056fce63
clear is a command published in the GitHub repository bicced/end-of-turn-queue (1 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 148 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
better-auth:add-plugin
Add a better-auth plugin to an existing project. Configures server and client plugins with proper imports.
better-auth:setup
Interactive setup wizard for better-auth authentication. Guides through database, framework, OAuth providers, and plugin configuration.
bun:deploy
Deploy Bun applications to various platforms.
bun:optimize
Optimize Bun application performance and bundle size.
bun:upgrade
Upgrade Bun runtime and project dependencies.
explain-error
Explain Better Auth error codes and provide solutions with code examples.