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/xsovad06/sova/agent-resumegit clone --depth 1 https://github.com/xsovad06/sovaWhat 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.00016 | $0.01672 |
| Opus 5 | $0.00008 | $0.00836 |
| Sonnet 5 | $0.00003 | $0.00334 |
| Haiku 4.5 | $0.00002 | $0.00167 |
Grade B, and why
agent-resume scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat .claude/agent-control/handoff.json 2>/dev/null How it starts
The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Resume
Read the current handoff state and determine what to do next. This is the "smart router" command -- it inspects the current state of a PR or issue and autonomously decides the next action.
ARGS: $ARGUMENTS
Instructions
You are an autonomous agent that picks up where a previous agent left off. Your job is to assess the current situation and take the appropriate next step.
1. Read Current State
Read all available state:
# Handoff from previous agent
cat .claude/agent-control/handoff.json 2>/dev/null
# Agent control status
cat .claude/agent-control/status.json 2>/dev/null
Parse the arguments -- they may include:
pr=<NUMBER>-- a specific PR to work onissue=<NUMBER>-- a GitHub Issue to work onwait_for=ci-- wait for CI checks to passinvestigate_ci=true-- investigate CI failures
2. Determine Situation
If a handoff exists, check its status:
awaiting_action-- previous agent finished but needs human decision. Assess if any action can be taken automatically based on the args.completed-- previous workflow is done. Check if there is follow-up work.failed-- previous agent failed. Diagnose and suggest recovery.
If no handoff exists, use the PR number or issue to assess the current state:
# Get PR state
gh pr view <PR_NUMBER> --json state,reviewDecision,statusCheckRollup,headRefName,baseRefName,mergeable,commits
# Check if branch is behind base
gh pr view <PR_NUMBER> --json mergeStateStatus --jq '.mergeStateStatus'
# Check CI
gh pr checks <PR_NUMBER>
# Check for review comments needing attention
gh api repos/<OWNER>/<REPO>/pulls/<PR_NUMBER>/comments --jq '[.[] | select(.in_reply_to_id == null)] | length'
gh api repos/<OWNER>/<REPO>/pulls/<PR_NUMBER>/reviews --jq '.[] | "\(.user.login): \(.state)"'
3. Act Based on Situation
PR is behind base branch -- rebase and push:
- Fetch latest base, rebase the PR branch, push with --force-with-lease
- If there are merge conflicts, attempt to resolve them (read each conflicted file, understand both sides of each conflict marker, resolve,
git add,git rebase --continue-- up to 3 rebase steps) - If resolution fails, run
git rebase --abortand write a failed handoff listing conflicting files - Write handoff with merge options
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.
- 2d ago First seen · 160 lines · 16 tokens per session scan B ae62be257cf1
agent-resume is a command published in the GitHub repository xsovad06/sova (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 16 tokens to every session and 1,672 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
doctor
Check the health of a KARIMO installation, identify issues, and provide actionable recommendations.
dashboard
Phase 3 monitoring — System health, execution insights, and velocity analytics.
run
Execute an approved PRD using feature branch workflow (v7.0). This command generates briefs, auto-reviews them, allows user iteration, and then orchestrates execution.
merge
Consolidate feature branch changes and create final PR to main. This completes the v5.0 feature branch workflow after all task PRs have been merged.
greptile-review
Execute the full Greptile review cycle on a PR, looping until score meets threshold or circuit breaker triggers.
feedback
Intelligent feedback capture with automatic complexity detection and adaptive investigation.