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/harehare/mq/rust-crategit clone --depth 1 https://github.com/harehare/mqWhat 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.00155 | $0.00155 |
| Opus 5 | $0.00077 | $0.00077 |
| Sonnet 5 | $0.00031 | $0.00031 |
| Haiku 4.5 | $0.00015 | $0.00015 |
Grade A, and why
mq rust-crate.instructions.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 2d 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
Rust Crate Coding Rules for mq
- Each crate must have a clear purpose and be documented in its
README.md(if present). - Organize code into logical modules; avoid large, monolithic files.
- Use
pub(crate)or tighter visibility unless wider exposure is necessary. - Prefer explicit error types using
miettefor user-facing errors. - Write comprehensive unit and integration tests in each crate.
- Document all public APIs with Rust doc comments.
- Avoid unsafe code unless absolutely necessary; document all unsafe blocks.
- Use feature flags for optional functionality.
- Keep dependencies minimal and up-to-date.
- Each crate should have its own
CHANGELOG.mdif it is published independently.
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.
- 2d ago First seen · 18 lines · 155 tokens per session scan A 1f22d194f27d
mq rust-crate.instructions.md is an instructions file published in the GitHub repository harehare/mq (1,023 stars, last pushed 2d ago), licensed MIT. It adds 155 tokens to every session, about $0.0008 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
webclaw CLAUDE.md
Claude Code instructions for 0xMassi/webclaw, covering webclaw, architecture, core modules (webclaw-core), fetch modules (webclaw-fetch) and llm modules (webclaw-llm).
speclens CLAUDE.md
Instructions for dansreis/speclens, covering claude.md, what it is, stack decisions, gates and file map.
HwpForge CLAUDE.md
Instructions for ai-screams/HwpForge, covering claude.md, project overview, architecture (forge metaphor), development commands and build & test.
scraps CLAUDE.md
Instructions for boykush/scraps, covering scraps development with claude code, project structure and development workflow.
kimun CLAUDE.md
Instructions for nico2sh/kimun, covering kimun, docs and rules.
mdscript CLAUDE.md
Instructions for dean0x/mdscript, covering mds (markdown script), build and test, release, land the bump on main via pr (ci-gated), then and gotchas.