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/shaun0927/opensafari/claude-mdgit clone --depth 1 https://github.com/shaun0927/opensafariWrote 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/shaun0927/opensafari/claude-md)<a href="https://agentmods.dev/instructions/shaun0927/opensafari/claude-md"><img src="https://agentmods.dev/badge/instructions/shaun0927/opensafari/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.00571 | $0.00571 |
| Opus 5 | $0.00285 | $0.00285 |
| Sonnet 5 | $0.00114 | $0.00114 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
opensafari 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Project Instructions
Branch Strategy
feature/* → develop → main (release)
- All PRs target
developbranch - Release merges go from
developintomain - Tag-based npm publish triggers on
main(v* tags)
Stacked / multi-part work
Avoid long chains of interdependent feature branches that each PR into the previous one. When 0.6.3 was cut, several PRs (#810/#811/#808/#812) were stranded outside develop by a stacked-PR topology and had to be rescued via a single catch-up integration PR (#814).
Rules to prevent recurrence:
- Each PR targets
developdirectly. Do not target another feature branch unless the base is already merged todevelop. - If work must be split into parts, land each part to
developbefore opening the next, or open them in parallel againstdevelopand resolve conflicts at merge time — never as a chain where part N depends on unmerged part N-1. - If a chain is unavoidable, the final integration PR must target
developand the intermediate branches must be deleted, not left as dangling bases. - Keep one logical concern per PR; do not bundle a refactor + feature + CI change so that a CI failure in one strands the others.
Build & Test
npm install && npm run build && npm test
Code Quality
- All source code, comments, commit messages, and PR descriptions must be in English
- Use
console.error()for logging —console.log()writes to stdout which carries MCP JSON-RPC and will corrupt the protocol - No
puppeteer-core,CDP, or Chrome dependencies — this project uses WebKit Remote Debugging Protocol - Use
Page.getCookies/Page.setCookie/Page.deleteCookie(NOT Network domain) - Use
Page.snapshotRectfor screenshots (NOTPage.captureScreenshot) - Use
document.createTouch()/document.createTouchList()(NOTnew Touch()) - Use
Runtime.awaitPromiseas separate command (NOT as parameter toRuntime.evaluate) simctl snapshot save/restoredoes NOT exist — usesimctl cloneor WebKit cookie export
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.
- 5d ago First seen · 53 lines · 571 tokens per session scan A ff9231153069
opensafari CLAUDE.md is an instructions file published in the GitHub repository shaun0927/opensafari (15 stars, last pushed 1mo ago), licensed MIT. It adds 571 tokens to every session, about $0.0029 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).