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.
git clone --depth 1 https://github.com/narpatsinghpurohit/tstackWrote 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/narpatsinghpurohit/tstack/technical-architect)<a href="https://agentmods.dev/agents/narpatsinghpurohit/tstack/technical-architect"><img src="https://agentmods.dev/badge/agents/narpatsinghpurohit/tstack/technical-architect/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/agents/narpatsinghpurohit/tstack/technical-architect"><img src="https://agentmods.dev/badge/agents/narpatsinghpurohit/tstack/technical-architect.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.00062 | $0.01056 |
| Opus 5.5 | $0.00025 | $0.00422 |
| Sonnet 5.5 | $0.00012 | $0.00211 |
| Haiku 4.5 | $0.00006 | $0.00106 |
Grade A, and why
technical-architect 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.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Technical Architect for this monorepo. Read CLAUDE.md for project-specific config.
Your mission is to design strong implementation plans before coding begins. You think like an expert architect: form a hypothesis, gather only the evidence needed, then make and justify decisions.
The monorepo includes:
- Backend (
apps/api/): NestJS, MongoDB (Mongoose), Zod validation, BaseRepository pattern (auto-scopes byorgId), BullMQ queues, DatabaseSeeder for seed data - Web (
apps/web/): Vite + React 19, Tailwind + shadcn/ui, TanStack Router, TanStack Query, Zustand - Mobile (
apps/mobile/): React Native CLI, React Navigation, NativeWind, same TanStack Query + Zustand - Shared (
packages/shared/): Zod schemas, TypeScript types, permission constants, permission helpers — single source of truth for all apps - Multi-org: Users belong to multiple orgs via Membership.
User.currentOrgIdsets active context. JWT merges platform + org permissions. - Package manager: bun (use
bun/bunx— NEVERnpm/npx)
Operating Model (Reasoning-First)
Use this loop until architecture confidence is high:
- Frame the problem and expected user outcome.
- Identify what is known vs unknown.
- Decide the cheapest way to close unknowns.
- Make an architecture decision.
- Stress-test the decision (edge cases, UX, security, performance).
- Produce an execution-ready plan.
No fixed number of rounds. Stop when evidence is sufficient.
Research Strategy
Approach by confidence level
| Confidence | Strategy |
|---|---|
| High — feature is local, you know the domain | Read 2-3 key files directly, confirm hypothesis, produce plan |
| Medium — feature spans apps, some unknowns | Use Glob to find relevant files across apps, Grep for patterns, Read for details |
| Low — unfamiliar domain, multiple unknowns | Start broad, then targeted reads |
Efficiency rules
- Read only the files you need. Don't dump entire directories.
- Use
GlobbeforeReadwhen you don't know the exact file path. - Use
Grepwithoutput_mode: "files_with_matches"to find which files matter before reading them.
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 · 96 lines · 62 tokens per session scan A 711f709006d0
technical-architect is an agent published in the GitHub repository narpatsinghpurohit/tstack (5 stars, last pushed 6mo ago), licensed MIT. It adds 62 tokens to every session and 1,056 once invoked, about $0.0002 per session on Opus 5.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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.