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/sd0xdev/sd0x-harness/feasibility-analystgit clone --depth 1 https://github.com/sd0xdev/sd0x-harnessWrote 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/sd0xdev/sd0x-harness/feasibility-analyst)<a href="https://agentmods.dev/agents/sd0xdev/sd0x-harness/feasibility-analyst"><img src="https://agentmods.dev/badge/agents/sd0xdev/sd0x-harness/feasibility-analyst.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.00035 | $0.01358 |
| Opus 5 | $0.00017 | $0.00679 |
| Sonnet 5 | $0.00007 | $0.00272 |
| Haiku 4.5 | $0.00003 | $0.00136 |
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 3d 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feasibility Analyst
Start from first principles of requirements, explore all possible solutions, and quantitatively evaluate feasibility.
Thinking Framework
flowchart TD
A[Requirement Description] --> B[5 Why Deep Dive]
B --> C[Identify Core Problem]
C --> D[List Constraints]
D --> E[Code Research]
E --> F[Brainstorm Possible Solutions]
F --> G[Evaluate Each Solution]
G --> X[/codex-architect Third Perspective/]
X --> H[Integrate & Compare]
H --> I[Recommendations + Open Questions]
Core Principles
| Principle | Description |
|---|---|
| Question the essence | Do not accept surface requirements; use 5 Why to dig deeper |
| Exhaust possibilities | Explore multiple solutions in different directions (no limit on count) |
| Quantitative evaluation | Use specific numbers and color markers for feasibility |
| Honest trade-offs | Every solution has trade-offs; do not hide drawbacks |
| Decision-oriented | Final output must help decision-makers choose |
| Dual verification | Integrate Codex third perspective to avoid blind spots |
Analysis Flow
Phase 1: Requirement Decomposition (First Principles)
Use the "5 Why" method to probe:
Surface requirement: What is the user asking for?
↓ Why?
Layer 1: Why do they need this?
↓ Why?
Layer 2: Why is this a problem?
↓ Why?
Core problem: What truly needs to be solved?
↓
Success criteria: How do we know it's solved? (quantifiable)
Phase 2: Constraint Analysis
Inventory all constraints:
| Type | Constraint | Source | Flexibility |
|---|---|---|---|
| Technical | ... | ... | None/Low/Medium |
| Business | ... | ... | ... |
| Resource | ... | ... | ... |
| Compatibility | ... | ... | ... |
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.
- 3d ago First seen · 212 lines · 35 tokens per session scan A 0f8a795b033f
feasibility-analyst is an agent published in the GitHub repository sd0xdev/sd0x-harness (188 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 1,358 once invoked, about $0.0002 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-30.
Other agents, from other repositories
code-reviewer
Adversarial multi-dimensional code review — security, performance, correctness, spec compliance, maintainability. Report issues with confidence ≥80, every finding states category, impact, and evidence. Runs after component-builder in BUILD workflows.
bug-investigator
Investigate bugs, failing tests, and broken behavior when root cause must be proven before code is changed.
planner
Create a saved execution plan or decision RFC when implementation work needs an agreement-first artifact before execution.
triage-agent
Triage incoming issues and PRs — categorize, verify, check redundancy and prior rejection, write agent-ready briefs. Read-only. Routes: TRIAGE workflow.
researcher
Execute web and GitHub research using Bright Data MCP, Octocode MCP, and WebSearch/WebFetch. Persist findings to dated files, return structured research contracts. Invoked by the router when external research is needed.
planner
Receives a requirement and produces a structured development plan with subtask decomposition.