state-manager

state-manager is a skill for Claude Code from AhmedHabiba/architor. It costs 59 tokens per session (1,657 once invoked), scanned A, original, MIT.

A state tracker for an architecture project. It records the current design phase, accepted decisions, component progress, and allowed phase changes in project files.

In plain words
What is it for?
Use it to check project status, track component acceptance, record decisions, validate phase transitions, and manage approved reopenings.
Why use it?
It gives the architecture workflow a reliable record of progress instead of depending on conversation history. This makes it clear what has been accepted and what work can happen next.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to check project status, track component acceptance, record decisions, validate phase transitions, and manage approved reopenings.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ahmedhabiba/architor/state-manager
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 AhmedHabiba/architor --skill state-manager
Clone the repo
git clone --depth 1 https://github.com/AhmedHabiba/architor

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 state-manager

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/ahmedhabiba/architor/state-manager"><img src="https://agentmods.dev/badge/skills/ahmedhabiba/architor/state-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,657 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.00059 $0.01657
Opus 5 $0.00030 $0.00829
Sonnet 5 $0.00012 $0.00331
Haiku 4.5 $0.00006 $0.00166

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

Security

Grade A, and why

state-manager 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 10d 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.

.claude/skills/state-manager/SKILL.md · 169 lines

How it starts

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

State Manager

State File: .arch/state.json

This file is the single source of truth for project progress. ALWAYS read it before responding to any architecture query. NEVER rely on conversation memory for phase state. ALWAYS update it after every state change.

Reading State

  • Parse the JSON file
  • Check current_phase to know where we are
  • Check phase-specific status fields for detail
  • For Phase 2, check sub_phase and individual acceptance flags (pattern_accepted, components_overview_accepted, cross_cutting_accepted)
  • For Phase 3, check components object for per-component status
  • Check reopens.count and reopens.max for reopen availability

Example – read state (pseudocode; use the Read tool, not code execution):

state = Read(".arch/state.json") → parse JSON
current_phase = state["current_phase"]

Valid Phase Transitions

not_started → evaluation     (when /analyze-prd runs)
evaluation → methodology     (when Phase 1 is accepted)
methodology → components     (when Phase 2 is fully accepted: pattern + components + cross-cutting)
components → finalization    (when ALL components accepted)

Backward transitions are ONLY allowed via /reopen (max 2 per project).

Phase 2 Sub-Phases

pattern → components_overview → cross_cutting

Each sub-phase is accepted independently via /accept. All three must be accepted for Phase 2 to be complete.

Component Status Values

pending → in_progress        (when /design-component starts)
in_progress → awaiting_acceptance  (when design is presented)
awaiting_acceptance → accepted     (when user accepts)
awaiting_acceptance → in_progress  (when user refines)
needs-review → in_progress         (after a reopen cascades)

Updating State

When updating state.json:

  1. Read current state
  2. Validate the transition is legal
  3. Write the updated state
  4. Increment decision_count if a decision was made

Example – validate and write state (pseudocode; use Read/Write tools, not code execution):

VALID_TRANSITIONS = {
  "not_started" → ["evaluation"],
  "evaluation"  → ["methodology"],
  "methodology" → ["components"],
  "components"  → ["finalization"],
}

state = Read(".arch/state.json") → parse JSON
current = state["current_phase"]

if new_phase not in VALID_TRANSITIONS[current]:
  # Invalid transition: do NOT write state.
  # Report the error to the user and stop.
  raise error: "Invalid transition: '{current}' → '{new_phase}'"

state["current_phase"] = new_phase
state["decision_count"] += 1
Write(".arch/state.json", JSON.stringify(state, indent=2))

Read the full file on GitHub · 169 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. 10d ago First seen · 169 lines · 59 tokens per session scan A c6b8553ffdaa

Subscribe to this mod's changes

state-manager is a skill published in the GitHub repository AhmedHabiba/architor (6 stars, last pushed 6mo ago), licensed MIT. It adds 59 tokens to every session and 1,657 once invoked, about $0.0003 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-31.

Related

Other skills, from other repositories

traction-eos

Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…

wondelai/skills · 147 tokens

promote-idea

Converts an album idea from IDEAS.md into an actual album project in one step. Use when the user says "promote [idea title]", "turn idea into album", or "start working on [idea]".

bitwize-music-studio/claude-ai-music-skills · 50 tokens

customer-onboarding-and-implementation

Takes a new customer from signature to working — setting a definition of live that both sides agreed before the contract was signed, planning and staffing the implementation, running data migration and integration realistically, training the people who will actually use it, and handing over to the ongoing…

cbrock84/headcount · 94 tokens

estimating-and-contingency

Produces a cost or effort estimate someone can defend — decomposing the work, choosing between analogous, parametric and bottom-up methods, documenting the basis and its assumptions, expressing confidence as a range, and sizing contingency and management reserve separately. Use this to build an estimate, challenge one…

cbrock84/headcount · 87 tokens

vendor-management

Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit. Use this to choose a vendor, run a selection process, structure a service agreement's operational terms, manage an underperforming supplier, plan an exit or migration, or…

cbrock84/headcount · 69 tokens

recap-doc

Post-development recap document generator. Use when: AI/Codex has implemented a feature and the user needs a guided walkthrough of what changed and why, with blind-spot detection and anticipated questions. Not for: Q&A follow-up (use /recap-ask), technical share-out for teammates (use /tech-brief), or generic code…

sd0xdev/sd0x-harness · 114 tokens