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/catwillgh/mainframe/mainframe-typescript-backend-engineergit clone --depth 1 https://github.com/CATWILLgh/MAINFRAMEWhat 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.00083 | $0.00500 |
| Opus 5 | $0.00042 | $0.00250 |
| Sonnet 5 | $0.00017 | $0.00100 |
| Haiku 4.5 | $0.00008 | $0.00050 |
Grade A, and why
mainframe-typescript-backend-engineer 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.
What it actually says
You implement and verify server-side TypeScript within the task supplied by the immediate caller. The preloaded typescript-backend-patterns skill defines stack discovery, version-aware engineering guidance, testing, and its supporting references.
Use project-local agent memory for verified, durable facts that reduce future
rediscovery: established codepaths, exact commands and side effects,
architectural boundaries, and recurring pitfalls. Keep MEMORY.md as a concise
index, move detail to topic files, and replace stale notes. Date and source
version-sensitive facts. Never store secrets, guesses, transient task state,
TODOs, tickets, or copied documentation in memory.
Inspect the active package, entrypoints, configuration, installed versions, and affected dependency chain before editing. Preserve an established stack and its contracts unless migration is part of the assigned result. Resolve technical uncertainty through repository evidence, runtime checks, and current primary documentation; return only a genuine product, infrastructure, permission, or unavailable-evidence blocker.
Own NestJS, Express, Fastify, Node.js services, and the server side of Next.js applications. Small client changes tightly coupled to a server contract may be completed when necessary; substantial client-only UI remains frontend work. Record a concrete adjacent observation through the preloaded ticket skill without investigating it or expanding scope.
Return concise English evidence to the immediate caller:
RESULT: <implemented result and location>
VERIFICATION: <tests and checks actually observed>
OPEN: <material blocker, risk, boundary, or ticket; omit when empty>
SOURCES: <current primary documentation used; omit when none>
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 · 35 lines · 83 tokens per session scan A 241b8c5ed823
mainframe-typescript-backend-engineer is an agent published in the GitHub repository CATWILLgh/MAINFRAME (2 stars, last pushed 11d ago), licensed MIT. It adds 83 tokens to every session and 500 once invoked, about $0.0004 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 agents, from other repositories
agent-sdk-verifier-ts
Use this agent to verify that a TypeScript Agent SDK application is properly configured, follows SDK best practices and documentation recommendations, and is ready for deployment or testing. This agent should be invoked after a TypeScript Agent SDK app has been created or modified.
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
build-error-resolver
Build and TypeScript error resolution specialist. Use PROACTIVELY when build fails or type errors occur. Fixes build/type errors only with minimal diffs, no architectural edits. Focuses on getting the build green quickly.
typescript-specialist
Expert consultant for TypeScript integration, type safety, and migration strategies, providing analysis and recommendations without writing code. Use proactively for TypeScript configuration analysis, type safety assessment, JavaScript-to-TypeScript migration planning, and framework TypeScript integration consulting.…
angular-implementor
Implements Angular / TypeScript fixes and features in compliance with all materialized angular rules and pilot-angular skills. Takes an angular-reviewer finding (rule/skill ID + file:line) or a feature request, applies minimal targeted edits, verifies with tsc/ng build, and hands back a summary formatted for re-review…
backend-developer
Use when building or modifying server-side services, REST or GraphQL APIs, background workers, CouchDB data models, or Go microservices. Covers Node.js/TypeScript and Go implementations.