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/go4cas/quiver/claude-mdgit clone --depth 1 https://github.com/go4cas/quiverWrote 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/go4cas/quiver/claude-md)<a href="https://agentmods.dev/instructions/go4cas/quiver/claude-md"><img src="https://agentmods.dev/badge/instructions/go4cas/quiver/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 | $0.00048 | $0.00048 |
| Opus 5 | $0.00024 | $0.00024 |
| Sonnet 5 | $0.00010 | $0.00010 |
| Haiku 4.5 | $0.00005 | $0.00005 |
Grade A, and why
quiver 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 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
Quiver — Claude Code context
All project context lives in AGENTS.md — the single source for every AI tool. Do not add conventions here; edit AGENTS.md instead.
@AGENTS.md
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 · 6 lines · 48 tokens per session scan A 7c7fb90f3be3
quiver CLAUDE.md is an instructions file published in the GitHub repository go4cas/quiver (5 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session, about $0.0002 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 instructions, from other repositories
OneJS AGENTS.md
AGENTS.md instructions for Singtaa/OneJS, covering onejs v3: agent guide, requirements, install, project setup and build and live reload.
vuestrata AGENTS.md
Instructions for boussadjra/vuestrata, covering using vite+, the unified toolchain for the web, built-in commands vs scripts, tool versions, review checklist and vuestrata project rules.
vuestrata CLAUDE.md
Instructions for boussadjra/vuestrata, covering claude.md, the one thing that trips people up, slash commands, verifying and testing reka-backed components.
vuestrata copilot-instructions.md
Instructions for boussadjra/vuestrata, covering copilot instructions, copilot-specific notes and before you finish.
OneJS CLAUDE.md
Claude Code instructions for Singtaa/OneJS: Agent guidance for this repository lives in AGENTS.md. Read it first.
vital AGENTS.md
Instructions for jvidalv/vital, covering ai agent development guide, quick reference, component creation workflow, step 1: determine component level and step 2: create component files.