models-and-agents

Rules for adding AI models and agents and changing the program's main work cycle. They specify where registrations belong, which tools agents may use, and how state changes must be defined.

In plain words
What is it for?
They guide provider registration, model detection, agent setup, tool restrictions, availability checks, and updates to documented limits and allowed state transitions.
Why use it?
They reduce the risk that new models, agents, or core-loop changes break existing behavior or silently grant too much access.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/hoangsonww/forge-agentic-coding-cli/models-and-agents
Clone the repo
git clone --depth 1 https://github.com/hoangsonww/Forge-Agentic-Coding-CLI

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 278 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00278
Opus 5 $0.00000 $0.00139
Sonnet 5 $0.00000 $0.00056
Haiku 4.5 $0.00000 $0.00028

Measured 2d ago against content hash 97216f1d8c5e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

models-and-agents 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.

.cursor/rules/models-and-agents.mdc · 32 lines

What it actually says

Model, agent, and core-loop rules

Providers (src/models/):

  • Register in src/models/registry.ts#initProviders. Add id to providerEnum. If local, add to isLocalProvider.
  • Classify model ids via src/models/local-catalog.ts — do not hand-roll regexes in a new provider.
  • Availability probe ≤ ~1.5 s.
  • HTTP via undici. Redact credentials via src/security/redact.ts.

Agents (src/agents/):

  • Register in src/agents/registry.ts. Extend src/agents/base.ts.
  • Declare narrow allowed tool sets. Never "all tools" to pass a test.

Core loop (src/core/):

  • Hot paths (loop.ts, mode-policy.ts, validation.ts): surgical edits only.
  • Mode-cap changes require updating the caps table in docs/ARCHITECTURE.md §4.
  • State transitions go in LEGAL_TRANSITIONS (src/persistence/tasks.ts). Never monkey-patch.
Changes

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.

  1. 2d ago First seen · 32 lines · 0 tokens per session scan A 97216f1d8c5e

Subscribe to this mod's changes

models-and-agents is a cursor rule published in the GitHub repository hoangsonww/Forge-Agentic-Coding-CLI (22 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 278 tokens. 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.