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/dills122/formly-contract/agents-mdgit clone --depth 1 https://github.com/dills122/formly-contractWrote 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/dills122/formly-contract/agents-md)<a href="https://agentmods.dev/instructions/dills122/formly-contract/agents-md"><img src="https://agentmods.dev/badge/instructions/dills122/formly-contract/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.00599 | $0.00599 |
| Opus 5 | $0.00300 | $0.00300 |
| Sonnet 5 | $0.00120 | $0.00120 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
formly-contract 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 2d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS
AI coding guidance for this repository.
Purpose
This repository builds Formly Contract: a compiler, MCP query surface, and Playwright integration for turning Angular Formly forms into reliable agent-readable E2E contracts.
Optimize for:
- deterministic, versioned semantic contracts with explicit evidence and unknowns
- reliable typed E2E intent that never depends on model-invented selectors
- small, explicit changes over broad refactors
- tests and documentation when behavior, contracts, setup, or commands change
Architecture Boundaries
Primary areas follow ADR 0008:
packages/schema/: versioned DTOs, runtime schemas, diagnostics, canonical serialization, and hashingpackages/compiler/: form registry, controlled Angular/Formly compilation, and allowlisted projectionpackages/workspace/: distributed discovery, generation, source indexing, and artifact assembly- future
packages/angular/: Angular-specific authoring and host integration - future
packages/mcp/: progressive read-only agent transport - future
packages/playwright/: validated-plan compilation, reviewed driver registries, and deterministic browser execution
Intent DTOs and validation policy belong in packages/schema/. Do not create
apps/mcp-server/, packages/test-intent/, or
packages/playwright-driver/; those historical paths were superseded by ADR
0008.
When a change spans areas, preserve ownership boundaries and update shared contracts first.
Contract-First Files
Treat these as interface contracts before implementation details:
docs/architecture-overview.mddocs/implementation-plan.md- the future versioned schemas under
packages/schema/
If behavior changes, update the relevant contract and docs in the same change.
Scope Control
- Keep changes localized to the requested behavior.
- Avoid unrelated refactors and generated artifact churn.
- Call out follow-up work separately from the current change.
- Do not change public interfaces, storage formats, route surfaces, or app names without explicit intent.
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.
- 2d ago First seen · 76 lines · 599 tokens per session scan A b3bfb0c54f05
formly-contract AGENTS.md is an instructions file published in the GitHub repository dills122/formly-contract (0 stars, last pushed 3d ago), licensed MIT. It adds 599 tokens to every session, about $0.0030 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
fundamental-ngx AGENTS.md
Instructions for SAP/fundamental-ngx, covering angular 22+ development guidelines, persona, quick reference, essential commands and build/lint/test specific library.
primitives CLAUDE.md
Instructions for radix-ng/primitives, covering radix ng primitives — claude guide, project knowledge, project overview, monorepo structure and naming conventions.
openbridge-webcomponents watch-radial-instruments.instructions.md
Instructions for Ocean-Industries-Concept-Lab/openbridge-webcomponents, covering watch & radial instruments, architecture overview, key principle: logic in watch.ts, instruments stay thin, shared sibling modules and layering & stacking pattern.
openbridge-webcomponents jsdoc.instructions.md
Instructions for Ocean-Industries-Concept-Lab/openbridge-webcomponents, covering jsdoc documentation rules, slots and events are consumer-critical (@slot / @fires), conditional properties (@availablewhen), what the tag does in storybook and comment style.
openbridge-webcomponents line-area-charts.instructions.md
Instructions for Ocean-Industries-Concept-Lab/openbridge-webcomponents, covering line/area charts & gauge trend, architecture overview, key principle: logic in base class, subclasses stay thin, base class architecture and line graph (non-filled).
openbridge-webcomponents automation-components.instructions.md
Instructions for Ocean-Industries-Concept-Lab/openbridge-webcomponents, covering automation components instructions, base class hierarchy, icon rendering pattern, state and readout getters and enums.