A session-change report that lists files changed during the current work session.

Reviewing changed files, seeing what happened to each one, and restoring individual files when needed.

It makes edits visible and provides a way to restore modified files to their earlier contents.

changes — Command by ARCASSystems

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 commands/arcassystems/founderos/changes

Clone the repo

git clone --depth 1 https://github.com/ARCASSystems/FounderOS

Made for: Claude Code.

Per session 82 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 414 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00082	$0.00414
Opus 5	$0.00041	$0.00207
Sonnet 5	$0.00016	$0.00083
Haiku 4.5	$0.00008	$0.00041

Measured yesterday against content hash 4c540f8b1dd0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

changes 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.

.claude/commands/changes.md · 41 lines

What it actually says

Changes - what did this session touch

Print the per-session change manifest: every file written this session, what happened to it, and how to put any of them back.

Procedure

Run:

python scripts/session_changes.py --print

(Use python3 where python is not found.)

Print the output verbatim. No commentary, no reformatting. The manifest is the artifact.
If it prints No session changes recorded yet., print that and stop.

How this works (context, not steps)

A PreToolUse hook snapshots each file's pre-edit bytes on the FIRST touch per session, into state/.snapshots/<session>/, and logs every write to state/.session-changes/<session>.jsonl.
A Stop hook renders state/session-manifest.md at session end. This command re-renders the most recent session's manifest on demand, so mid-session it reflects the session so far.
Restore any modified file to its pre-session state:
```
python scripts/session_changes.py --restore <path> --session <sid>
```
The manifest prints the exact command per file. A file created this session has no snapshot - delete it to undo.
None of this needs git. On a git-full install it runs as a second net under save/history/restore.

Rules

Read-only apart from the tracker's own runtime state under state/.
No other skills.
No em dashes or en dashes. Hyphens only.

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.

yesterday First seen · 41 lines · 82 tokens per session scan A 4c540f8b1dd0

Subscribe to this mod's changes

changes is a command published in the GitHub repository ARCASSystems/FounderOS (5 stars, last pushed 18d ago), licensed MIT. It adds 82 tokens to every session and 414 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-31.

Git and workflow Productivity ai-agents claude-code founder-os llms-txt markdown operating-system

wiki-query

Ask questions against the wiki. Synthesizes answers from wiki pages with cross-reference citations.

zosmaai/pi-llm-wiki · 18 tokens

wiki-digest

Generate a daily or weekly digest of wiki changes — new sources, pages, insights, and gaps.

zosmaai/pi-llm-wiki · 20 tokens

demo-command

Example slash command that wraps the demo-skill. Showcases the command kind.

crystian/skill-map · 22 tokens

ingest-l1

L1 analysis loop for the abapwiki knowledge base: for each batch it launches the abap-analyzer sub-agent in parallel, then the adversarial judge abap-deepcheck (separate session), applies only the analyses that pass the fail-closed gate, and commits. Resumes exactly after an interruption. Use this skill to document…

Gixsy95/abap_wiki · 86 tokens

web-search

Search fetched web-source Markdown by regex and pull surrounding context for the best hits. Optionally restrict to one source alias.

raintree-technology/docpull · 24 tokens

docs-refresh

Re-fetch a cached source, ignoring the 7-day cache. Use when upstream content has changed.

raintree-technology/docpull · 20 tokens