Borrowing it
Nothing to install: this file belongs to julianromli/droid-factory-template. 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/julianromli/droid-factory-template/main/AGENTS.mdgit clone --depth 1 https://github.com/julianromli/droid-factory-templateWrote 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/julianromli/droid-factory-template/agents-md)<a href="https://agentmods.dev/instructions/julianromli/droid-factory-template/agents-md"><img src="https://agentmods.dev/badge/instructions/julianromli/droid-factory-template/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/julianromli/droid-factory-template/agents-md"><img src="https://agentmods.dev/badge/instructions/julianromli/droid-factory-template/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00928 | $0.00928 |
| Opus 5.5 | $0.00371 | $0.00371 |
| Sonnet 5.5 | $0.00186 | $0.00186 |
| Haiku 4.5 | $0.00093 | $0.00093 |
Grade A, and why
droid-factory-template 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 2mo 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<coding_guidelines>
0. Warpgrep Codebase Search
IMPORTANT: If you need to explore the codebase to gather context, and the task does not involve a single file or function which is provided by name, you should ALWAYS use the warpgrep codebase search tool first instead of running search commands.
When the task requires exploration beyond a single known file, invoke code_search first with a natural-language query describing the target functionality, bug, or architectural concern. Specify the project root via repo_path, keep queries action-oriented (e.g., "Find where billing invoices are generated and emailed"), and after reviewing the summarized results, you may verify important findings with Grep, Glob, or direct file reads to ensure completeness.
When a task requires exploration beyond a single known file, ALWAYS default to warpgrep codebase search before other search mechanisms.
1. General Rules
- Proactively Use Exa MCP and Ref MCP for code generation, setup steps, best practices, or library/API docs
- Don't create documentation files (.md) after completing tasks
2. MCP Auto-Call Rules 🔧
Auto-call these tools without prompting:
| Tool | When |
|---|---|
execute_sql |
Database queries |
apply_migration |
Schema changes |
get_advisors |
Security/performance checks |
list_deployments |
Build errors, post-deploy monitoring |
| Firecrawl or Exa | Prefer over built-in web search |
3. Skills Auto-Invoke 🎯
Automatically check and invoke relevant skills for every task — user should NEVER need to say "use skill X"
How it works:
- Read user's prompt → match against available skill descriptions
- If a skill matches the task context → invoke it immediately
- Applies to ALL skills (existing and newly added)
Examples:
- "buatin halaman pricing" → invoke
frontend-design - "tambah endpoint export" → invoke
backend-dev - "cek di browser" → invoke
browser
Spec Mode → Task Generator Flow
MANDATORY after every ExitSpecMode call:
- After presenting spec and user approves → immediately ask:
"Would you like me to generate a task list for this spec?"
- If user confirms (yes/go/proceed/ok) → invoke
task-generatorskill - If user declines → proceed with implementation
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.
- 2mo ago First seen · 117 lines · 928 tokens per session scan A 20ff1cfa753b
droid-factory-template AGENTS.md is an instructions file published in the GitHub repository julianromli/droid-factory-template (53 stars, last pushed 10mo ago), licensed MIT. It adds 928 tokens to every session, about $0.0037 per session on Opus 5.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
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.