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/rajconnects/founder-stack/sessionsgit clone --depth 1 https://github.com/rajconnects/founder-stackWhat 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.00022 | $0.00534 |
| Opus 5 | $0.00011 | $0.00267 |
| Sonnet 5 | $0.00004 | $0.00107 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
sessions 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are inspecting parallel-session state.
Arguments: $ARGUMENTS (default: list)
Subcommands
list (default)
- Read
.claude/coordination.json. - Print a table:
ID STATUS SEVERITY PHASE BRANCH HEARTBEAT (age) sess-abc active major 2a phase-2a-billing 2m sess-def completed minor docs main — sess-ghi completed_unclean major 1c phase-1c-auth 18m (stale) - Below the table, list any rows where
status: activeand heartbeat age > staleness threshold — these are likely crashed sessions.
show <id>
Print the full row for <id> as pretty JSON. Resolve <id> against either id or resume_id (substring match OK).
clean
- Read
.claude/coordination.json. - For each row with
status: activeand heartbeat older than_doc.staleness_threshold_minutes:- Flip to
completed_unclean, setcompletedto now.
- Flip to
- For each
completed_uncleanrow whoseworktreepath exists on disk and is registered ingit worktree list:- Run
git worktree remove --force '<path>'. Capture stderr.
- Run
- Print a summary:
Swept N stale rows. Removed M worktrees. K paths needed manual cleanup: - <path>: <reason> - Surface anything that needs the user's eyes — never silently delete uncommitted work in a worktree without warning. If
git worktree removecomplains about uncommitted changes, do not add--forceautomatically; report and ask.
Notes
- This command is read-mostly.
cleanis the only writer beyond status flips. Never mutate theclaimsof another session — those are owned by their writer. - Heartbeat ages are computed against the system clock at command run.
/sessions cleanis the only sweep mechanism in v0.1. A scheduled background script is on the roadmap; until then, run/sessions cleanmanually whenlistshows stale rows.
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 · 47 lines · 22 tokens per session scan A fcb86c97bb7d
sessions is a command published in the GitHub repository rajconnects/founder-stack (2 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 534 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.