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 instructions/quickerhub/quicker-rpc/claude-mdgit 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/instructions/quickerhub/quicker-rpc/claude-md)<a href="https://agentmods.dev/instructions/quickerhub/quicker-rpc/claude-md"><img src="https://agentmods.dev/badge/instructions/quickerhub/quicker-rpc/claude-md.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.1 | $0.00226 | $0.00226 |
| Opus 5 | $0.00113 | $0.00113 |
| Sonnet 5 | $0.00045 | $0.00045 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
quicker-rpc CLAUDE.md 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 6d 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
Quicker / qkrpc (MCP)
You have qkrpc MCP tools when this project or ~/.claude/ is configured via qkrpc agent setup.
Start: qkrpc_health → on failure qkrpc_wait (no repeated shell probes).
Authoring: docs action=get topics overview → authoring-workflow. Step-runner: qkrpc_step_runner_search → qkrpc_step_runner_get — never guess inputParams.
Disk edit: read layout via MCP resource quicker://workspace/readme or docs topic workspace-editing. Edit .quicker/ data.json / files/ with your file tools → workspace_program action=patch.
Refresh skills/rules after CLI upgrade: qkrpc agent setup --upgrade
Guide: docs/agent-mcp-integration.md in quicker-rpc repo.
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.
- 6d ago First seen · 20 lines · 226 tokens per session scan A c3dbe92072c8
quicker-rpc CLAUDE.md is an instructions file published in the GitHub repository QuickerHub/quicker-rpc (13 stars, last pushed 22d ago), licensed MIT. It adds 226 tokens to every session, about $0.0011 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 instructions, from other repositories
vscode tree-widgets.instructions.md
Use when asked to consume workbench tree widgets in VS Code.
vscode accessibility.instructions.md
Use when implementing accessibility features, ARIA labels, screen reader support, accessible help dialogs, or keybinding scoping for accessibility. Covers AccessibleContentProvider, CONTEXTACCESSIBILITYMODEENABLED, verbosity settings, and announcement patterns.
vscode writing-tests.instructions.md
VS Code test writing guidelines — unit tests, integration tests, snapshot tests, and clean teardown patterns. Reference when writing or updating tests.
vscode notebook.instructions.md
Architecture documentation for VS Code notebook and interactive window components. Use when working in src/vs/workbench/contrib/notebook/.
vscode interactive.instructions.md
Architecture documentation for VS Code interactive window component. Use when working in src/vs/workbench/contrib/interactive.
vscode design-philosophy.instructions.md
VS Code design philosophy — the shared Values→Principles→Moves vocabulary for reasoning about UI in design terms rather than raw pixels. Use when creating, editing, or reviewing any visual surface (CSS, DOM, theming, icons, motion). Name the value/principle before reaching for a token.