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/adilkalam/orca/orca-statusgit clone --depth 1 https://github.com/adilkalam/orcaWrote 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.
[](https://agentmods.dev/commands/adilkalam/orca/orca-status)<a href="https://agentmods.dev/commands/adilkalam/orca/orca-status"><img src="https://agentmods.dev/badge/commands/adilkalam/orca/orca-status.svg" alt="Measured on agentmods" height="20"></a>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.00007 | $0.00821 |
| Opus 5 | $0.00003 | $0.00411 |
| Sonnet 5 | $0.00001 | $0.00164 |
| Haiku 4.5 | $0.00001 | $0.00082 |
Grade A, and why
orca-status 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/orca-status - Recording Session Status
PURPOSE: Show current recording session status including session ID, state, step count, and files touched.
EXPECTED OUTCOME: Quick status overview of the active recording session.
Step 1: Check Recording Layer Status
Verify orca-record binary exists:
if [ ! -f ~/.claude/bin/orca-record ]; then
echo "orca-record not installed. Run: cd ~/.claude && ./install.sh"
exit 0
fi
Verify git repository:
if ! git rev-parse --git-dir >/dev/null 2>&1; then
echo "Not in a git repository. Recording layer requires git."
exit 0
fi
Step 2: Execute Status Command
Run orca-record status:
~/.claude/bin/orca-record status
Expected CLI output format:
Session: sess-19c6983c46029c7
State: ACTIVE
Started: 2026-02-17T14:30:00.000Z
Steps: 5
Files touched: 12
Step 3: Format Output for User
Display formatted status:
Recording Status
Session: sess-19c6983c46029c7
State: ACTIVE
Started: 2026-02-17 14:30
Steps: 5
Files touched: 12
State values:
ACTIVE- Active session, events being recordedIDLE- No active sessionENDED- Session completed
Step 4: No-Session Case
If no active session:
Recording Status
No active recording session.
Recording starts automatically when you begin working.
Use /continue to see previous sessions.
Step 5: Surface Continuity State (active-task.md is primary)
Recording is telemetry; the primary continuity artifact is active-task.md. Surface its
freshness so the user knows whether /session-resume will restore intent:
AT=.orca/orchestration/active-task.md
if [ -f "$AT" ]; then
mtime=$(stat -f %m "$AT" 2>/dev/null || stat -c %Y "$AT" 2>/dev/null)
age_h=$(( ( $(date +%s) - mtime ) / 3600 ))
if [ "$age_h" -lt 48 ]; then
echo "active-task.md: present, ${age_h}h old -- fresh; run /session-resume to restore intent"
else
echo "active-task.md: present, ${age_h}h old -- stale (>48h); re-run /session-save"
fi
else
echo "active-task.md: none -- run /session-save to capture intent for the next session"
fi
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.
- 3d ago First seen · 140 lines · 7 tokens per session scan A d3647b061f2f
orca-status is a command published in the GitHub repository adilkalam/orca (2 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 821 once invoked, about $0.0000 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
git
Git operations with intelligent commit messages and workflow optimization.
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.