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/go4cas/quiver/add-componentgit clone --depth 1 https://github.com/go4cas/quiverWhat 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.00000 | $0.00354 |
| Opus 5 | $0.00000 | $0.00177 |
| Sonnet 5 | $0.00000 | $0.00071 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
add-component 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
Create a new Quiver component named: $ARGUMENTS
The argument is a PascalCase component name (e.g. PostCard, StatusBadge). If it is not PascalCase, convert it.
Follow these steps exactly:
- Create
src/components/<Name>.js:
import { html } from '@arrow-js/core'
export function <Name>({ /* props */ }) {
return html`
<div>
<!-- component content -->
</div>
`
}
- Derive sensible props from the component name
- Apply all Arrow.js rules:
- Wrap reactive props in
() =>only if the prop value can change after render; static props (strings, numbers passed once) do not need() => - No
<!-- -->HTML comments inside the template literal — use JS comments above it instead - Use
aria-disabled+ CSS for disabled states, never.disabled="${...}"
- Wrap reactive props in
- Use Tailwind CSS utility classes for styling; match the visual style of existing components in
src/components/ - Annotate the component's props with JSDoc, e.g.
/** @param {{ title: string }} props */— strictcheckJsis enforced and untyped props failnpm run typecheck
- Verify — run and fix any failures:
npm run typecheck && npm test && npm run test:e2e
- Report:
- The file created
- A one-line usage example:
import { <Name> } from '../components/<Name>.js'(import directly — there is no barrel file) - Any props the component accepts
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 · 38 lines · 0 tokens per session scan A 46bbc135524e
add-component is a command published in the GitHub repository go4cas/quiver (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 354 tokens. 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.