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/quickerhub/quicker-rpc/explain-actiongit clone --depth 1 https://github.com/QuickerHub/quicker-rpcWrote 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/quickerhub/quicker-rpc/explain-action)<a href="https://agentmods.dev/commands/quickerhub/quicker-rpc/explain-action"><img src="https://agentmods.dev/badge/commands/quickerhub/quicker-rpc/explain-action.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.00014 | $0.00194 |
| Opus 5 | $0.00007 | $0.00097 |
| Sonnet 5 | $0.00003 | $0.00039 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
explain-action 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
Explain the Quicker action matching: $ARGUMENTS (or the @-mentioned action when arguments are empty).
Read-only — do not patch, run, debug, or write files.
- Resolve the action/subprogram id (
qkrpc_action_query/ get or subprogram get). - Read program body from disk (
workspace_program read_data) or get sync when needed. - Summarize: purpose, variables, step flow (module keys + key params), and non-obvious wiring.
Use plain language; no markdown tables. Cite step_runner_get when module param names matter.
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 · 16 lines · 14 tokens per session scan A e4cad24603b8
explain-action is a command published in the GitHub repository QuickerHub/quicker-rpc (13 stars, last pushed 21d ago), licensed MIT. It adds 14 tokens to every session and 194 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-30.
Other commands, from other repositories
review
Review current changes for correctness, style, and potential issues.
extend
Capture a mid-PR sub-idea and implement it onto the current open PR's branch — no new branch, no new PR. Preserves Verify → Review → Deliver.
security-review
Depth-first security audit of the current git diff — OWASP Top 10, secret leakage, insecure-by-default APIs, and language-specific foot-guns. Pass a PR number to audit a specific PR's diff.
sync
Bring the current branch up to date with the default branch — delegates the mechanical merge/rebase to rimba (or git), then walks through any conflicts file-by-file with a recommended resolution before applying. Never auto-pushes. Pass --rebase to rebase instead of merge. Pass --check-redundancy to also surface…
pre-ship
Run the pre-ship quality gate checklist before publishing your agent.
plan
Take the following feature description and create a comprehensive, structured implementation plan.