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 agents/icoretech/airbroke/typescript-and-uigit clone --depth 1 https://github.com/icoretech/airbrokeWrote 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/agents/icoretech/airbroke/typescript-and-ui)<a href="https://agentmods.dev/agents/icoretech/airbroke/typescript-and-ui"><img src="https://agentmods.dev/badge/agents/icoretech/airbroke/typescript-and-ui.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.00000 | $0.00333 |
| Opus 5 | $0.00000 | $0.00167 |
| Sonnet 5 | $0.00000 | $0.00067 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
typescript-and-ui 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 4d 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
TypeScript and UI
TypeScript Baseline
- TypeScript runs in
strictmode - Use the
@/alias for project imports - Keep type-only imports separate when possible because Biome warns on mixed import style
components/ui/**is excluded from the TypeScript project, so changes there need extra manual attention
Component Boundaries
- Default to server components and server helpers unless the code needs browser APIs, client-side interactivity, or React hooks
- Mark interactive files with
"use client"explicitly - Keep mutations in server actions and feed the result back through refresh, revalidation, or redirect flows instead of duplicating server state locally
- Do not import server-only helpers such as
lib/db.tsor auth internals into client components
UI Stack
- Shared primitives live under
components/ui/ - The project is configured for shadcn components with the
base-novapreset, Base UI primitives, CSS variables, Lucide icons, andapp/globals.css components/ai-elements/**is also skipped by Biome, so treat it like a vendor-style surface: edit sparingly and verify the consumer manually
Practical Rules
- Prefer existing primitives and wrappers before adding a new UI abstraction
- Keep route-specific charts, filters, and dialogs close to the feature they serve, then extract only when they become shared
- When a UI file must stay client-side, keep data fetching and secret-bearing work on the server and pass only the minimum data down
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.
- 4d ago First seen · 37 lines · 0 tokens per session scan A 0f1059c6ed1e
typescript-and-ui is an agent published in the GitHub repository icoretech/airbroke (222 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 333 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.
Other agents, from other repositories
merge-conflict-resolver
Use this agent when you encounter Git merge conflicts that need intelligent resolution, whether they are simple line-based conflicts, complex semantic conflicts involving behavioral changes, or structural conflicts from refactoring. This agent should be used proactively when merge operations fail due to conflicts, or…
git-conflict-resolver
Use this agent when you need to resolve git merge conflicts, merge branches, or handle complex git operations involving branch integration. This includes resolving conflicts in files, choosing between conflicting changes, merging feature branches into main/master, rebasing branches, or cleaning up merge-related…
trigger-dev-expert
Use this agent when you need to design, implement, or optimize background jobs and workflows using Trigger.dev framework. This includes creating reliable async tasks, implementing AI workflows, setting up scheduled jobs, structuring complex task hierarchies with subtasks, configuring build extensions for tools like…
form
FORM — Design. Visual system, UI architecture, motion, accessibility, design PRDs. Use when a human will see the work, when a landing page or product UI is requested, or when Forge is about to invent a look. Use proactively for any user-facing surface.
axis
AXIS — Architecture. System design, ADRs, irreversible calls, architectural review. Use when the shape of the system is unset, when a shortcut would lock us in, or before Forge writes a feature that spans boundaries. Use proactively for any new product or service.
forge
FORGE — Software engineering. Production code, tests, refactors, bug fixes after the cause is known. Use when the design and architecture are set and the job is to make it real. Use proactively for implementation once Axis/Form have spoken.