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.
npx agentmods add commands/postindustria-tech/agentic-toolkit/create-stategit clone --depth 1 https://github.com/postindustria-tech/agentic-toolkitWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00018 | $0.00651 |
| Opus 5 | $0.00009 | $0.00326 |
| Sonnet 5 | $0.00004 | $0.00130 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
create-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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create LangGraph State Schema
Generate a TypedDict state schema with proper type hints, Annotated fields, and optional Pydantic validation.
Instructions for Claude
1. Gather Information
Ask user for:
- State class name (if not provided)
- State fields (if
--fieldsnot provided):- Field name
- Type (str, int, float, List[...], dict, etc.)
- Whether append-only (use
Annotated[List, operator.add]) - Whether custom reducer needed
2. Read Settings
Check .claude/langgraph-dev.local.md for:
code_style(pydantic_v2 or pydantic_v1)include_type_hints(default: true)include_docstrings(default: true)
3. Generate State Schema
Create file {state_name.lower()}_state.py with:
from typing import TypedDict, List, Annotated, Optional
from langchain.schema import BaseMessage
import operator
class {StateName}(TypedDict):
\"\"\"State schema for {state_name} workflow.\"\"\"
# Add fields based on user input
messages: Annotated[List[BaseMessage], operator.add] # If append-only
current_step: str
# ... other fields
4. Add Validators (if Pydantic requested)
If user wants validation:
from pydantic import BaseModel, Field, field_validator
class {StateName}State(BaseModel):
messages: List[BaseMessage] = Field(description="Conversation messages")
confidence: float = Field(ge=0, le=1, description="Confidence score 0-1")
@field_validator('confidence')
def validate_confidence(cls, v):
if not 0 <= v <= 1:
raise ValueError('Confidence must be between 0 and 1')
return v
5. Add Helper Functions
Include:
def create_initial_state(**kwargs) -> {StateName}:
\"\"\"Factory for creating initial state with defaults.\"\"\"
return {
"messages": [],
"current_step": "start",
**kwargs
}
def validate_state(state: {StateName}) -> bool:
\"\"\"Validate state integrity.\"\"\"
# Add validation logic
return True
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.
- yesterday First seen · 102 lines · 18 tokens per session scan A 02e27e668922
create-state is a command published in the GitHub repository postindustria-tech/agentic-toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 651 once invoked, about $0.0001 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.