agentmods.dev

create-feasibility

create-feasibility is a skill for Claude Code from tomzx/agents. It costs 21 tokens per session (1,420 once invoked), scanned A, original, MIT.

A structured check of whether a proposed software feature is technically, financially, and operationally practical before detailed requirements are written.

In plain words
What is it for?
Use it to assess a GitHub issue or feature proposal using the existing codebase, architecture, project context, and available design documents.
Why use it?
It helps identify major costs, risks, and system constraints before the team commits significant project time.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions subagents; positional $N argument.

not rated 13repo changed 20d ago A scan 21 tokens original MIT

Good fit Use it to assess a GitHub issue or feature proposal using the existing codebase, architecture, project context, and available design documents.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tomzx/agents/create-feasibility
View source ↗ tomzx/agents tomzx.github.io
Install

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.

Any agent
npx skills add tomzx/agents --skill create-feasibility
Clone the repo
git clone --depth 1 https://github.com/tomzx/agents

Made for: Claude Code.

Wrote 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.

agentmods badge for create-feasibility

README.md
[![agentmods](https://agentmods.dev/badge/skills/tomzx/agents/create-feasibility/github.svg)](https://agentmods.dev/skills/tomzx/agents/create-feasibility)
Your own site
<a href="https://agentmods.dev/skills/tomzx/agents/create-feasibility"><img src="https://agentmods.dev/badge/skills/tomzx/agents/create-feasibility/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.

agentmods 80×15 button for create-feasibility

Your own site · 80×15
<a href="https://agentmods.dev/skills/tomzx/agents/create-feasibility"><img src="https://agentmods.dev/badge/skills/tomzx/agents/create-feasibility.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,420 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.01420
Opus 5.5 $0.00008 $0.00568
Sonnet 5.5 $0.00004 $0.00284
Haiku 4.5 $0.00002 $0.00142

Measured 20d ago against content hash 8e41e6de0389, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-feasibility 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 20d 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.

skills/create-feasibility/SKILL.md · 109 lines

How it starts

The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create Feasibility Assessment

Produces a structured feasibility assessment for a proposed feature, evaluating technical, financial, and operational viability before the project invests in full requirements gathering. Acts as a go/no-go gate.

Prerequisites

  • Apply the shared SDLC conventions in skills/sdlc/references/shared.md.
  • If no argument is provided, use $ISSUE_TITLE and $ISSUE_BODY as the feature description (and $ISSUE_NUMBER to link the feature).
  • A reviewed, prioritized GitHub issue or feature description provided as $1
  • .sdlc/features/N-<slug>/requirements.md, existing-solutions.md, and codebase-analysis.md when available: the codebase analysis in particular provides input to the cost and risk of changing existing code
  • Read any files present under .sdlc/context/ (project-overview.md, architecture.md, conventions.md) for project-level context
  • Apply any artifact style rules found in conventions.md to the produced document

When to Skip

Skip this phase, and record a one-line note naming the signal, when the issue is maintainer-authored with acceptance criteria, the criteria are already settled, and the change reuses existing internal code with a stated budget. The verdict this phase would return (a go, with the issue's own budget as the estimate) is already implied, so the note is the record rather than a full assessment.

Steps

  1. Read the issue or feature description. Fetch from GitHub if a URL is provided.
  2. Read .sdlc/context/architecture.md to understand the current system and technology stack.
  3. Read .sdlc/context/project-overview.md to understand project scope and constraints.
  4. Read .sdlc/features/N-<slug>/codebase-analysis.md when available, and carry its changeability assessments and migration risks into the technical and effort estimates below.
  5. Assess technical feasibility: can the feature be built with the current stack and integrations? Are there unknowns that require a spike?
  6. Assess financial feasibility: what is the estimated effort (S/M/L/XL)? Are there infrastructure, licensing, or third-party costs?
  7. Assess operational feasibility: does the team have the skills and availability? Does it fit the roadmap? What is the maintenance burden?
  8. For each dimension, assign a verdict: Feasible / Feasible with conditions / Not feasible.
  9. Record assumptions that the feasibility assessment depends on but has not verified. For each assumption that carries meaningful risk (e.g., "the existing ORM supports this query pattern", "the third-party API has no rate limits below our expected volume", "the team has the required expertise"), promote it via /create-assumption so it is tracked and can be validated before implementation.
  10. Derive the overall go/no-go decision. If any dimension is "Not feasible", the overall verdict is "No-go". If any dimension is "Feasible with conditions", list the conditions.
  11. Derive the feature directory name N-<slug> following the Feature Directory Naming convention in skills/sdlc/references/shared.md: use the issue number as N when one is available, otherwise a p-prefixed sequence number (p1, p2, ...) marking the feature as pending a placeholder issue. Record the related issue number in the frontmatter issue field only when an issue exists.
  12. Write the output to .sdlc/features/N-<slug>/feasibility.md, creating the directory if it does not exist.

Read the full file on GitHub · 109 lines

Changes

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.

  1. 20d ago Changed · +5 lines 8e41e6de0389
  2. 22d ago Changed · +12 lines a4e935167340
  3. 24d ago Changed 21cefc266f10
  4. 27d ago Changed 0166bc84c411
  5. 2mo ago First seen · 92 lines · 21 tokens per session scan A eba3debc44d5

Subscribe to this mod's changes

create-feasibility is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 1,420 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.

Planning
Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens