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/ineersa/re-search/agents-mdgit clone --depth 1 https://github.com/ineersa/re-searchWrote 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/ineersa/re-search/agents-md)<a href="https://agentmods.dev/instructions/ineersa/re-search/agents-md"><img src="https://agentmods.dev/badge/instructions/ineersa/re-search/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 | $0.01155 | $0.01155 |
| Opus 5 | $0.00577 | $0.00577 |
| Sonnet 5 | $0.00231 | $0.00231 |
| Haiku 4.5 | $0.00115 | $0.00115 |
Grade A, and why
re-search 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 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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
re-search
This project uses the Symfony UX frontend stack. Six agent skills are installed to help you work with it.
Which tool to use
- Pure JS behavior, no server round-trip -- use the
stimulusskill - Navigation, partial page updates -- use the
turboskill - Reusable static UI component -- use the
twig-componentskill - Reactive component that re-renders on user input -- use the
live-componentskill - Not sure which one fits -- use the
symfony-uxskill (orchestrator / decision tree) - Browser automation / UI testing -- use the
playwright-cliskill via Task tool withsubagent_type: "playwright-cli"
Key rules
- Always render
{{ attributes }}on the root element of a LiveComponent - Prefer HTML syntax (
<twig:Alert />) over Twig syntax ({% component 'Alert' %}) - Use
data-model="debounce(300)|field"for text inputs in LiveComponents - Stimulus controllers must clean up listeners and observers in
disconnect() - Turbo Frame IDs must match between the page and the server response
- Use Turbo Streams when updating multiple page sections; use Frames for a single section
<twig:Turbo:Stream:Append>syntax is available since Symfony UX 2.22+- In PHPUnit tests, always use static assertion calls (
self::assert*) instead of instance calls ($this->assert*) to keep PHPStan clean. - MATE tools (mandatory): Logs, profiler, PHPStan, PHPUnit, and Composer MUST use the
mate-toolsskill and its wrapper script (.cursor/skills/mate-tools/scripts/mate-tool-call.sh). NEVER usemake test,make phpstan, or directvendor/bincommands for these. - Infrastructure operations (setup, up/down, console, doctrine) MUST use
maketargets (no directdocker compose execfor these) - NEVER run Composer on the host — Composer MUST run inside the Docker container only (via
make composer-*or MATEcomposer-*tools) - NEVER run PHP on the host — All PHP commands (phpunit, phpstan, console, etc.) MUST run inside the container
- For browser testing and UI verification, ALWAYS use Task tool with
subagent_type: "playwright-cli" - NEVER compile assets in development environment; the
make tailwind-watchprocess handles this automatically - DO NOT run
make assets-compileduring development; only do this in production builds
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 · 70 lines · 1,155 tokens per session scan A daf58830a62c
re-search AGENTS.md is an instructions file published in the GitHub repository ineersa/re-search (5 stars, last pushed 5mo ago), licensed MIT. It adds 1,155 tokens to every session, about $0.0058 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
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.