TrueForge is an agent runtime that runs the execution loop connecting language models, tools, skills, sandboxes, approvals, context handling, and session state. Developers use it through a chat interface, HTTP API, TypeScript SDK, or embeddable UI to build and operate AI agents.
Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/truefoundry/trueforgenpx agentmods add rules/truefoundry/trueforge/trueforge-ui-slotsWrote 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/rules/truefoundry/trueforge/trueforge-ui-slots)<a href="https://agentmods.dev/rules/truefoundry/trueforge/trueforge-ui-slots"><img src="https://agentmods.dev/badge/rules/truefoundry/trueforge/trueforge-ui-slots/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/rules/truefoundry/trueforge/trueforge-ui-slots"><img src="https://agentmods.dev/badge/rules/truefoundry/trueforge/trueforge-ui-slots.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.00000 | $0.00323 |
| Opus 5.5 | $0.00000 | $0.00129 |
| Sonnet 5.5 | $0.00000 | $0.00065 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
trueforge-ui-slots 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 1mo 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.
What it actually says
Slotted UI components (useSlot)
Every newly created or newly JSX-bearing component in @truefoundry/trueforge-ui
MUST be host-overridable through the slots system. Do not hard-import leaf UI into
layouts/containers when a slot exists (or should exist).
Checklist for a new / newly JSX component
- Export the component and augment
AtomSlotsin the same file:
declare module '../theme/SlotsProvider.js' {
interface AtomSlots {
MyComponent: typeof MyComponent;
}
}
- Register the default in
src/theme/defaultSlots.ts. - Parents render it via
useSlot('MyComponent'), never a direct import of the default implementation (except insidedefaultSlots.ts). - Keep the public prop surface stable so hosts can swap the implementation.
Examples
// ❌ BAD — layout hard-wires a leaf
import { AgentsLibraryButton } from '../atoms/AgentsLibraryButton.js';
<AgentsLibraryButton compact />
// ✅ GOOD — host can override
const AgentsLibraryButton = useSlot('AgentsLibraryButton');
<AgentsLibraryButton compact />
Primitives that are already slotted (Button, SearchInput, etc.) follow the same rule when exposed as named atoms; internal helpers with no JSX need no slot.
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.
- 1mo ago First seen · 44 lines · 0 tokens per session scan A 053d71fb244f
trueforge-ui-slots is a cursor rule published in the GitHub repository truefoundry/trueforge (6,248 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 323 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-09-02.
Other cursor rules, from other repositories
hatch3r-component-conventions
Component structure, styling tokens, loading/error/empty states, form validation timing, and accessible label patterns for Vue, React, and JSX.
diagram
Generate or update a mermaid diagram with the .mmd text as source of truth — defaults to a lightweight zero-dependency Node live-preview server that watches the .mmd and hot-reloads a browser tab (pan/zoom), with a self-hosted mermaid.live editor via Docker, system-viewer SVG, VS Code live preview, or a public…
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.