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/seanhogg/builderforce.ai/agents-mdgit clone --depth 1 https://github.com/SeanHogg/Builderforce.aiWrote 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/seanhogg/builderforce.ai/agents-md)<a href="https://agentmods.dev/instructions/seanhogg/builderforce.ai/agents-md"><img src="https://agentmods.dev/badge/instructions/seanhogg/builderforce.ai/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.00376 | $0.00376 |
| Opus 5 | $0.00188 | $0.00188 |
| Sonnet 5 | $0.00075 | $0.00075 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
Builderforce.ai 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 3d 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 — 16 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engineering rules
These rules apply to every change in this repository.
Required design principles
- DRY: Keep each policy, transformation, contract, and reusable UI behavior in one canonical implementation. Reuse or extract shared code instead of copying logic or markup. Do not introduce an abstraction until there is a real shared responsibility.
- SOLID: Keep units focused, extend behavior through explicit interfaces and composition, preserve substitutability, expose narrow consumer-specific contracts, and depend on abstractions at architectural boundaries. Avoid multipurpose components, broad service interfaces, and hidden coupling.
- N-layer architecture: Preserve the presentation → application → domain → infrastructure dependency direction. Presentation code owns view state, application code coordinates use cases, domain code owns business rules, and infrastructure code implements storage and runtime adapters. Domain code must not depend on presentation or infrastructure details.
- Localization: All user-visible copy must come from the localization system. Add or update keys in every supported locale catalog in the same change. Do not hard-code labels, placeholders, notices, accessibility text, tooltips, or empty/error states in UI components.
- Registry-driven localization: Any registry, configuration array, or data model that stores localization keys must have a focused test which resolves every referenced key against every supported locale. Catalog-to-catalog parity is not sufficient because a key can be absent from all catalogs. Adding or changing a
labelKey,titleKey,descriptionKey, or equivalent is incomplete until the source-to-catalog test passes.
Completion check
Before considering work complete, review changed code for duplication, responsibility leakage, layer violations, and untranslated user-facing strings. Treat violations as blockers and run the relevant typechecks and focused tests. When a change touches localized copy or a localization-key registry, frontend/src/i18n/messages.test.ts is a required focused test.
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.
- 3d ago First seen · 16 lines · 376 tokens per session scan A c7cd9f4ba552
Builderforce.ai AGENTS.md is an instructions file published in the GitHub repository SeanHogg/Builderforce.ai (5 stars, last pushed today), licensed MIT. It adds 376 tokens to every session, about $0.0019 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.