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.
git clone --depth 1 https://github.com/bhanu91221/sfdx-iqWrote 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/bhanu91221/sfdx-iq/handoff)<a href="https://agentmods.dev/commands/bhanu91221/sfdx-iq/handoff"><img src="https://agentmods.dev/badge/commands/bhanu91221/sfdx-iq/handoff.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.1 | $0.00012 | $0.00674 |
| Opus 5 | $0.00006 | $0.00337 |
| Sonnet 5 | $0.00002 | $0.00135 |
| Haiku 4.5 | $0.00001 | $0.00067 |
Grade A, and why
handoff 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 6d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/handoff
Generate a structured session summary so the next conversation can pick up exactly where this one left off. Captures what was built, what decisions were made, and what's next.
Usage
/handoff Display session summary in chat
/handoff --save Display summary AND write to HANDOFF.md in project root
Workflow
Step 1: Gather Session Context
Collect the session's work automatically:
# What files changed this session
git diff --name-only HEAD~1 HEAD 2>/dev/null || git status --short
# Recent commit history (if any commits were made)
git log --oneline -5 2>/dev/null
# Current branch
git branch --show-current 2>/dev/null
Also scan for:
- Any newly created files in this session
- Errors or blockers encountered
- Agent outputs from the session
Step 2: Generate Handoff Document
Produce the following structured summary:
# Session Handoff — [Date]
## What Was Built
<!-- List each file created or significantly modified, one line per file -->
- `force-app/main/default/classes/AccountService.cls` — Created service layer with processAccounts() and updateIndustry()
- `force-app/main/default/classes/AccountServiceTest.cls` — Test class with 92% coverage
## Decisions Made
<!-- Key architectural or implementation decisions and WHY -->
- Used `inherited sharing` on AccountService to allow callers to control sharing context (AccountController uses `with sharing`, batch uses `without sharing`)
- Chose Queueable over @future for sync because callout is needed after DML
- TestDataFactory pattern adopted: created TestDataFactory.cls for reuse across test classes
## What's Next
<!-- Incomplete work, next steps, open questions -->
- [ ] Add OpportunityService.cls following same pattern as AccountService
- [ ] Wire AccountController.getAccounts() to accountSummaryCard LWC component
- [ ] Run full org test suite before deploying: `sf apex run test --test-level RunLocalTests`
- [ ] Review if AccountSelector needs a custom index on Industry field (high-volume org)
## Files Changed This Session
<!-- Auto-populated from git diff -->
[list from git diff]
## How to Resume
At the start of your next session, say:
"Read HANDOFF.md and continue from where we left off on [feature name]."
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.
- 6d ago First seen · 102 lines · 12 tokens per session scan A 098bd5925376
handoff is a command published in the GitHub repository bhanu91221/sfdx-iq (2 stars, last pushed 3mo ago), licensed MIT. It adds 12 tokens to every session and 674 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
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
music-suno-prompt
Grounded Suno prompt synthesis from local knowledge corpus + persona canon + label canon. No vibes-prompting.