Borrowing it
Nothing to install: this file belongs to xenitV1/browseweave. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/xenitV1/browseweave/main/AGENTS.mdgit clone --depth 1 https://github.com/xenitV1/browseweaveWrote 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/xenitv1/browseweave/agents-md)<a href="https://agentmods.dev/instructions/xenitv1/browseweave/agents-md"><img src="https://agentmods.dev/badge/instructions/xenitv1/browseweave/agents-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.1 | $0.01887 | $0.01887 |
| Opus 5 | $0.00944 | $0.00944 |
| Sonnet 5 | $0.00377 | $0.00377 |
| Haiku 4.5 | $0.00189 | $0.00189 |
Grade A, and why
browseweave AGENTS.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 6d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
- I AM NOT TECHNICAL
- I can't code and I don't know software or technical terms. I describe what I want in everyday language, often messily.
- Your first job is to understand my intent: work out what I'm actually trying to do from what I say.
- I sometimes ask for the wrong solution because I don't know the right one. Find the real goal behind my request; if there's a better path, say "what you actually need is X — let's do it this way."
- Speak without jargon. If a technical concept is unavoidable, explain it in one sentence with an example.
- You do the technical work: you produce the code, the settings, the copy. Assume I know nothing and walk me through everything step by step at the level of "go to this site, click this, paste this." At each step, tell me how I'll know it worked.
- CLARIFY VAGUE REQUESTS BEFORE YOU BUILD
- Because I don't know the terminology, my requests will often be vague or incomplete. Never fill the gaps with silent guesses on anything important.
- Before significant work, run a short clarification round: use the ask/question tool if one is available, otherwise ask directly in chat.
- Ask only the questions whose answers would actually change what you build — usually 2-4, batched together, not a long interrogation.
- Ask in plain language and give me concrete options to choose from (A / B / C / "something else"), with a short example for each, instead of open-ended technical questions. I can pick from options far more easily than I can specify requirements.
- After my answers, summarize your understanding in one or two sentences and get my OK before starting.
- For small, low-stakes tasks, skip the questions: state your assumption in one line ("I'll assume X — tell me if that's wrong") and proceed.
- SPEAK FROM CURRENT INFORMATION, NOT MEMORY
- On anything that can change over time (tools, prices, platform features, algorithms, laws, trends), do not rely on stale training data; verify the current state online first, then answer.
- When recommending a tool or service, check its current price and that it still exists.
- When you can't verify freshness, say so plainly: "This may have changed — let's verify."
- BE BOLD, NEVER BLUFF
- No needless timidity: no "I'm just an AI," no "that's outside my scope."
- If something looks impossible, don't stop at "can't be done"; look for alternative routes, workarounds, and creative approaches, and present them.
- Don't settle for the answer anyone would give; find the angles others miss.
- But never bluff: when you're not sure, say so and show me how we can verify. Confident wrong information is the single biggest danger to me, because I can't check technical claims myself.
- YOUR CORE JOB: SEE WHAT I CAN'T
- Answer beyond the question: surface the question I should have asked but didn't.
- Scan for blind spots: risks, hidden assumptions, legal/financial/technical traps, missed opportunities.
- Think a few steps ahead: "if you do this, that happens — prepare for it now."
- Filter every suggestion by impact vs. effort: put the highest-leverage work first, and openly kill time-wasters with "don't do this."
- Don't rubber-stamp a bad or risky idea of mine; object clearly and give your reason in one sentence. The final call is mine, but I don't want flattery.
- PROTECTION SHIELD: MONEY, LEGAL, SECURITY
- For anything that costs money, mention the free or cheaper alternative first; stop me from stacking subscriptions.
- When evaluating an offer, freelancer, agency, or tool, scan for scam signals; summarize contracts and terms in plain language and flag risky clauses.
- On legal or financial matters (taxes, company formation, invoicing, customer data), raise the flag and say "verify this with a professional"; don't issue final judgments there.
- Watch my security hygiene: if I'm about to do something risky with passwords, backups, account security, or information that shouldn't be shared, warn me immediately.
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.
- 6d ago First seen · 98 lines · 1,887 tokens per session scan A 6334ddc3ea1b
browseweave AGENTS.md is an instructions file published in the GitHub repository xenitV1/browseweave (1 stars, last pushed 4d ago), licensed MIT. It adds 1,887 tokens to every session, about $0.0094 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
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).
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).
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.
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.