business-evaluation

business-evaluation is a skill for Claude Code, Codex from duc01226/EasyPlatform. It costs 34 tokens per session (3,797 once invoked), scanned A, a copy of template-skill, MIT.

A project-guidance skill that tells Codex how to load repository documents and follow project workflows. It also defines rules for task tracking, user questions, and required skill steps.

In plain words
What is it for?
Use it when coding, planning, debugging, testing, or reviewing a repository that has project-specific guidance.
Why use it?
It gives the coding agent the project context and operating rules it needs instead of relying on documents being added automatically.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths; mentions subagents; installed under .agents/ (shared by several agents).

Good fit Use it when coding, planning, debugging, testing, or reviewing a repository that has project-specific guidance.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/duc01226/easyplatform/business-evaluation
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 duc01226/EasyPlatform --skill business-evaluation
Clone the repo
git clone --depth 1 https://github.com/duc01226/EasyPlatform

Made for: Claude Code, Codex.

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 business-evaluation

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/duc01226/easyplatform/business-evaluation"><img src="https://agentmods.dev/badge/skills/duc01226/easyplatform/business-evaluation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,797 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 81% copy Near-identical to another mod 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.00034 $0.03797
Opus 5.5 $0.00014 $0.01519
Sonnet 5.5 $0.00007 $0.00759
Haiku 4.5 $0.00003 $0.00380

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

Security

Grade A, and why

business-evaluation 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.

Origin

This is a copy

81% identical to template-skill — 204 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/business-evaluation/SKILL.md · 217 lines

How it starts

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

Codex compatibility note:

  • Invoke $skill-name: load the registered .agents/skills/<name>/SKILL.md and execute it with Codex tools; no separate Skill tool or Claude mode switch is needed. Author .claude/**; mirrors are generated.
  • Track steps before execution and keep progress/evidence current. Explicit skill requests execute their protocol. Use the native question tool for required questions.
  • Map foreign tool names to available host capabilities. A name mismatch needs no approval; an actually unavailable required capability stops with its step/evidence and a user question before adaptation.
  • Subagent authorization: when a skill is user-invoked or AI-detected and its protocol requires subagents, that skill activation authorizes use of the required spawn_agent subagent(s) for that task.
  • Preserve protocol order unless the user approves a deviation. Workflows use $start-workflow: gates stay fixed; other steps may flex with logged reasons and evidence.

[BLOCKING] Execute declared steps in order. NEVER skip, reorder, or merge without explicit user approval. [BLOCKING] Before each step/sub-skill call, update todo tracking: set in_progress at start, completed at end. [BLOCKING] Every completed/skipped step MUST include brief evidence or explicit skip reason. [BLOCKING] If Task tools unavailable, maintain equivalent step tracker with same status transitions.

Quick Summary

Goal: Evaluate business idea viability; deliver evidence-backed viability verdict—score, confidence, Pursue/Pivot/Pause/Pass recommendation—grounded in complete 9-block BMC, 3-year financials + assumptions, 5+ risks with mitigation + residual risk, phased execution + GTM plan, so go/no-go rests on traced evidence, never optimism.

Summary:

  • Order: Seven evaluation steps, preceded by a market-evidence precondition: load market evidence first, then run ALL 7 evaluation steps in order — detect idea/scope/evidence completeness; (1) capture idea (problem/solution/target), (2) 9-block BMC, (3) 3-year financials + assumptions, (4) 5+ risks + mitigation/residual risk, (5) phased execution, (6) GTM, (7) verdict. NEVER skip, reorder, or merge — why: partial evaluation invalidates the decision.
  • Market gate: In workflow parent, read exact MARKET_ANALYSIS_PATH ({plan-dir}/research/market-analysis.md only copy fallback); standalone, use supplied path. If absent, state $market-analysis did not run, mark TAM/SAM/SOM, share, and segment size N/A, cap verdict confidence at 60%; NEVER re-derive sizing.
  • Evidence gate: all 9 BMC blocks cite proof; every financial number has assumption + source; each 5+ risk has mitigation + residual risk; unbacked artifact fails.
  • Decision/output: verdict = 1-10 score + confidence tier (95/80/60/<60%) + basis + Pursue/Pivot/Pause/Pass + key success condition; write to docs/knowledge/strategy/business/{descriptive-slug}.md via enforced .claude/templates/business-evaluation-template.md, then ask user question tool for next route (domain-analysis recommended); NEVER auto-decide, favor skepticism.

Workflow:

Before evaluation — detect + reason: classify supplied idea, scope, and market evidence as present, missing, or ambiguous; for each step run focused Think: evidence / economics / execution / decision passes. Derive concerns from idea + evidence; required blocks/categories guide coverage, not checklist recitation.

Precondition — load market analysis: In workflow-research business-eval mode, read exact parent-provided MARKET_ANALYSIS_PATH ({plan-dir}/research/market-analysis.md only copy fallback); in another workflow, read the exact path market-analysis returned in this run (or its {plan-dir}/research/market-analysis.md copy); standalone, use explicitly supplied path. Absent → do NOT re-derive: state $market-analysis did not run; mark every market-sizing figure (TAM/SAM/SOM, share, segment size) N/A with that reason; cap verdict confidence at 60%.

Read the full file on GitHub · 217 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. 3d ago Changed · -163 lines 81e3416b2a22
  2. 1mo ago First seen · 380 lines · 34 tokens per session scan A 01b40b7cf876

Subscribe to this mod's changes

business-evaluation is a skill published in the GitHub repository duc01226/EasyPlatform (12 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 3,797 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 81% identical to template-skill, differing in 204 lines, and is treated as a copy.

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