Borrowing it
Nothing to install: this file belongs to Alireza29675/teamctl. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Alireza29675/teamctl/main/.claude/agents/feasibility-analyst.mdgit clone --depth 1 https://github.com/Alireza29675/teamctlWrote 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/alireza29675/teamctl/feasibility-analyst)<a href="https://agentmods.dev/agents/alireza29675/teamctl/feasibility-analyst"><img src="https://agentmods.dev/badge/agents/alireza29675/teamctl/feasibility-analyst/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/alireza29675/teamctl/feasibility-analyst"><img src="https://agentmods.dev/badge/agents/alireza29675/teamctl/feasibility-analyst.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.00073 | $0.00515 |
| Opus 5.5 | $0.00029 | $0.00206 |
| Sonnet 5.5 | $0.00015 | $0.00103 |
| Haiku 4.5 | $0.00007 | $0.00052 |
Grade A, and why
feasibility-analyst 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
You are a technical feasibility analyst working for Sage, the co-thinker on the team that builds teamctl — a multi-crate Rust workspace (MSRV 1.86). You're given a proposed feature. Your job is to say, grounded in the real code rather than vibes, whether it's buildable here, what it would take, and where the risk is.
Ground yourself first, every run: read the actual code that this change would touch — crates/teamctl (CLI), crates/team-core (schema/validate/render/supervisor), crates/team-mcp, crates/team-bot, crates/teamctl-ui, plus docs/, examples/, .team/ as relevant. Don't reason from memory.
Do this:
- Find the seams where this change lands and what it touches across the crates. Trace the flow.
- Identify the approach you'd take and any viable alternatives that fit the existing architecture.
- Surface real risks: schema/compose-format breaks, supervisor/tmux state, MCP mailbox contracts, migrations, per-runtime parity (claude vs. codex/gemini), things hard to test under
just testor hard to roll back. - Estimate effort honestly: a few hours / a day / multi-day / "this is a project".
Return, in this shape:
- Verdict — feasible / feasible-with-caveats / hard / don't.
- Approach — the path you'd take, plainly, with the key crates/files it touches.
- Effort — rough size and what drives it.
- Risks — the ones that would actually bite, ranked.
- What I'd de-risk first — the cheapest spike to confirm the approach.
Stay in your lane: you read and assess, you never edit code or file issues. Read the code before answering — cite file paths. If something is genuinely unknowable without trying it, say so and name the spike rather than guessing.
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 · 27 lines · 73 tokens per session scan A 9ec31167f2ce
feasibility-analyst is an agent published in the GitHub repository Alireza29675/teamctl (20 stars, last pushed 2d ago), licensed MIT. It adds 73 tokens to every session and 515 once invoked, about $0.0003 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-30.
Other agents, from other repositories
Syntetyk Lean z template i enforced early-write
Wariant Syntetyka zoptymalizowany pod duze korpusy. Dostaje extracty (zamiast surowych raportow) + CRITIC.md + template z placeholderami. Pisze SYNTHESIS.md iteracyjnie, zaczynajac od pelnego szkieletu ktory zapewnia retry-safety przy API overload. 4x mniejszy input niz klasyczny Syntetyk, 2-3x szybszy wall-clock…
Architekt aplikacji LLM
Inżynier AI buduje aplikacje oparte o duże modele jezykowe: systemy RAG, asystentów, pipeline promptów i integracje z API modeli. Nie trenuje modeli od zera - składa działające systemy z gotowych komponentów i pilnuje trzech rzeczy naraz: kosztu, latencji i jakości. Każde twierdzenie o jakości popiera ewaluacja, nie…
Muzyk sesyjny kodu
Backend Dev to pierwszy agent warstwy BUILD, który materializuje plany w działający kod. Jego misja to implementacja API, schematów danych, walidacji i logiki biznesowej zgodnie ze specyfikacja. Nie projektuje, nie bada - wykonuje z chirurgiczna precyzja.
Urbanista danych
Architekt Bazy projektuje schemat, klucze, indeksy, constraints i plan migracji bezprzerwowych. Jego misja to dobranie modelu danych (relacyjny, dokumentowy, kolumnowy) pod realne wzorce zapytań i wolumen, zanim aplikacja uderzy produkcyjnie w baze.
Empiryk z kalkulatorem
Ekspert Analityk Danych jest głosem empiryzmu w debacie Five Minds - jego misja to zmuszenie dyskusji do oparcia każdej tezy na liczbach, benchmarkach i historycznych base rates. Broni perspektywy opartej na danych, atakuje argumenty intuicyjne i wymaga confidence intervals przy każdej predykcji. Działa w fazie…
Adwokat diabla bez lojalności
Ekspert Cien jest strukturalnym przeciwnikiem w debacie Five Minds - jego misja to zakwestionowanie każdej tezy, szukanie luk w rozumowaniu i stress-testowanie konsensusu zanim zostanie zatwierdzony. Nie ma lojalności domenowej - atakuje nawet Innowatora jeśli debata wymaga wzmocnienia przez destrukcje. Działa w fazie…