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/betterthantomorrow/joyride/flaresgit clone --depth 1 https://github.com/BetterThanTomorrow/joyrideWrote 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/betterthantomorrow/joyride/flares)<a href="https://agentmods.dev/instructions/betterthantomorrow/joyride/flares"><img src="https://agentmods.dev/badge/instructions/betterthantomorrow/joyride/flares.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.02021 | $0.02021 |
| Opus 5 | $0.01010 | $0.01010 |
| Sonnet 5 | $0.00404 | $0.00404 |
| Haiku 4.5 | $0.00202 | $0.00202 |
Grade A, and why
joyride flares.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 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 263 lines · 2,021 tokens per session scan A 174545ef4624
joyride flares.instructions.md is an instructions file published in the GitHub repository BetterThanTomorrow/joyride (592 stars, last pushed 4d ago), with no licence file. It adds 2,021 tokens to every session, about $0.0101 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
calva-backseat-driver AGENTS.md
Instructions for BetterThanTomorrow/calva-backseat-driver, covering calva backseat driver - ai agent guide, essential architecture, action/effect system ("ex"), runtime state structure and datascript connections.
calva-backseat-driver backseat-driver-source-conventions.instructions.md
Backseat Driver extension source code conventions — Ex framework patterns, async, state management, namespace separation, and naming. Supplements universal Clojure patterns with Backseat Driver-specific rules.
calva-backseat-driver copilot-instructions.md
Instructions for BetterThanTomorrow/calva-backseat-driver, covering what backseat driver is, repl environment, state inspection safety, bundled ai context (chatskills / chatinstructions) and key development commands.
calva-backseat-driver changelog.instructions.md
CHANGELOG.md conventions — audience, scope, and entry format for the Backseat Driver extension changelog.
hulunote AGENTS.md
Instructions for hulunote/hulunote, covering north star, issues and prs (format), read before you act, repo map (high level) and default workflow expectations.
awesome-vscode CLAUDE.md
Instructions for viatsko/awesome-vscode, covering claude.md, what this repo is, adding an entry, themes and linting / ci.