framework/engineering/skills/flowai-analyze-context/SKILL.md
Analyze total token usage including conversation history, system prompts, and active rules to estimate cost.
npx skillsauth add korchasa/flow flowai-analyze-contextInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Scope: Analyze ALL components that contribute to the context window and cost. This includes:
AGENTS.md and any active .cursor/rules.<open_and_recently_viewed_files>, <git_status>, or other automatic context blocks.Estimation Method:
Token Count = Character Count * MultiplierProcedure:
AGENTS.md and any active rule files to estimate their size.Tools:
deno run scripts/count_tokens.ts "TEXT_snippet"
Total Chars * 0.3.User: "How many tokens are we using?" Action:
AGENTS.md (~3000 chars) + Rules (~1000 chars).12,000 * 0.3 = 3,600 tokens.tools
Delegate a task to another AI IDE's CLI (codex / claude / opencode / cursor-agent) through an isolated-context subagent. Triggers on "delegate to <ide>", "have <ide> do <task>", "execute <task> in <ide>", "offload to <ide>". For one-shot relay or fan-out comparison use `ai-ide-runner` instead.
tools
Run prompts in Claude Code, OpenCode, Cursor, or Codex CLIs from the current session — pick one IDE, fan out across several, or compare models. You are a courier that relays the other runtime's stdout verbatim, do not synthesise your own answer. Use on "run in <ide>", "compare <ide> vs <ide>", "try on <model>", "which IDE handles X better", "run across models".
tools
Recommend which LLM model to use for a task. Use when asked "which model / best LLM for X", "pick a model for this task", or for a model shortlist ranked by live leaderboard evidence (coding, reasoning, agentic, tool-use, price, speed). Live-fetches public leaderboards and ranks models with per-axis rationale and citations.
development
Produce a comprehensive Product Requirements Document (PRD). Use when the user asks to write a PRD or formalize a feature's scope, goals, and success metrics.