current_state

A business-analysis guide for describing how an organization works today, including its problems, needs, and likely root causes.

In plain words
What is it for?
Use it to document an as-is process, define a business need, investigate why a problem happened, or support root-cause analysis.
Why use it?
It helps turn a vague problem into a clear picture of the current situation and what needs to change.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/chaussky/ainalyst/current_state
Any agent
npx skills add chaussky/ainalyst --skill current_state
Clone the repo
git clone --depth 1 https://github.com/chaussky/ainalyst

Made for: Claude Code, Codex.

Per session 84 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,253 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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 $0.00084 $0.02253
Opus 5 $0.00042 $0.01126
Sonnet 5 $0.00017 $0.00451
Haiku 4.5 $0.00008 $0.00225

Measured 2d ago against content hash 0af4cbb9b82e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

current_state 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 2d 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/current_state/SKILL.md · 244 lines

The source is not reproduced here

Licensed AGPL-3.0

The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 2d ago First seen · 244 lines · 84 tokens per session scan A 0af4cbb9b82e

Subscribe to this mod's changes

current_state is a skill published in the GitHub repository chaussky/ainalyst (41 stars, last pushed 7d ago), licensed AGPL-3.0. It adds 84 tokens to every session and 2,253 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

business-requirements-analyst

Complete methodology for software and business requirements gathering. Use when you need to document a new project, validate a business idea, create technical specifications, or generate complete documentation covering business vision, stakeholders, processes, functional and non-functional requirements, data model…

gmdaos/business-requirements-analyst · 79 tokens

ba-concept-model

Use this skill whenever a business analyst, architect, or project team needs to identify, define, and structure the core business objects (concepts) of a domain — even if they don't use that exact term. Trigger on phrases like: "what are the key things the business manages", "define our business objects", "build a…

plausibleba/ba-skills · 180 tokens

ba-capability-mapping

Use this skill whenever a business analyst, architect, or project team needs to produce a Capability Map — even if they don't use that exact term. Trigger on phrases like: "map out what the business does", "identify our capabilities", "build a capability model", "what capabilities do we need for this initiative"…

plausibleba/ba-skills · 158 tokens

ba-value-streams

Use this skill whenever a business analyst, architect, or project team needs to identify, map, or analyse value streams — even if they don't use that term. Trigger on phrases like: "map out how we deliver value", "end-to-end process", "customer journey from our side", "how does a booking become a completed stay"…

plausibleba/ba-skills · 172 tokens

ba-taxonomy-standard

Shared conventions used across all PlausibleBA skills. Load this skill whenever producing, validating, or comparing any PlausibleBA taxonomy — Capability Maps, Concept Models, Value Streams, or any other structured artefact. It defines the numbering system, column order, naming conventions, MECE rules, and XLSX…

plausibleba/ba-skills · 80 tokens

ba-plausibleba

Use this skill when someone wants to run a complete business architecture session — producing a Capability Map, Concept Model, and Value Stream in one guided flow. Trigger on phrases like: "run PlausibleBA", "build my business architecture", "I want a full BA model", "run all three", or when someone invokes…

plausibleba/ba-skills · 105 tokens