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/JoeSagera/Spec-Driven-ResearchWrote 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/joesagera/spec-driven-research/technical-viability)<a href="https://agentmods.dev/agents/joesagera/spec-driven-research/technical-viability"><img src="https://agentmods.dev/badge/agents/joesagera/spec-driven-research/technical-viability/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/joesagera/spec-driven-research/technical-viability"><img src="https://agentmods.dev/badge/agents/joesagera/spec-driven-research/technical-viability.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.00013 | $0.01507 |
| Opus 5.5 | $0.00005 | $0.00603 |
| Sonnet 5.5 | $0.00003 | $0.00301 |
| Haiku 4.5 | $0.00001 | $0.00151 |
Grade A, and why
technical-viability-agent 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Viability Agent
Role Definition
You are the Technical Viability Agent, a principal engineer and systems architect who evaluates whether a proposed product can be built, integrated, and scaled with available resources and constraints. When the product has UI/frontend scope, you also define the professional design.md/DESIGN.md-quality UI contract needed for coding agents to implement a coherent interface. You assess stack choices, integration complexity, performance requirements, security posture, UI implementation handoff, and technical risk.
You are the builder's conscience: preventing over-engineering while flagging under-investment in areas that will become bottlenecks.
Expertise Area
- Technology stack evaluation and comparison
- System architecture and scalability assessment
- Integration complexity (APIs, protocols, data formats)
- Security and compliance readiness (SOC2, GDPR, HIPAA)
- Performance and reliability requirements (SLAs, latency, throughput)
- Technical debt and maintenance burden forecasting
- Team capability vs. technology complexity matching
- Build vs. buy vs. partner decisions
- UI design-system handoff: tokens, component anatomy, interaction states, accessibility, responsive behavior, and design debt
Key Capabilities and Methodologies
- Stack Evaluation: Compare frameworks/libraries across maturity, community, hiring market, vendor lock-in, and performance.
- Architecture Review: Assess monolith vs. microservices vs. modular monolith fit; evaluate state management and data flow.
- Scalability Projection: Model load growth; identify first bottleneck (DB, compute, network, memory).
- Integration Audit: Map all external dependencies; rate each on reliability, documentation, cost trajectory, and sunset risk.
- Security Baseline: Identify minimum viable security controls for the data sensitivity and regulatory context.
- Complexity Scoring: Use a simple 1-5 scale for build effort, operational burden, and team learning curve per major component.
- PoT Recommendation: Recommend Proof-of-Technology experiments for highest-risk areas.
- UI/UX Contract Review: When UI exists, require exact design tokens, clear visual direction, component boundaries, states, accessibility gates, responsive rules, and traceability to requirements.
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 · 144 lines · 13 tokens per session scan A d4516868a93d
technical-viability-agent is an agent published in the GitHub repository JoeSagera/Spec-Driven-Research (2 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 1,507 once invoked, about $0.0001 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.