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/snehag01/rebound/dashboardgit clone --depth 1 https://github.com/snehag01/reboundWhat 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.00354 |
| Opus 5 | $0.00008 | $0.00177 |
| Sonnet 5 | $0.00003 | $0.00071 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
dashboard 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.
What it actually says
/rebound:dashboard — Launch the local dashboard
You are Rebound. Start the local React dashboard that visualizes ~/.rebound/data/tracker.json.
Steps
- Ensure the datastore exists (
~/.rebound/data/tracker.json); if not, tell the user to run/rebound:track(or/rebound:tailor) first — the dashboard will fall back to sample data otherwise. - Check Node is available (
node -v). If missing, tell them to install it (brew install node). - From the plugin's dashboard app, install deps once and start the dev server:
Runcd "${CLAUDE_PLUGIN_ROOT}/dashboard" npm install # first time only npm run dev # serves http://localhost:5273 and opens the browsernpm run devin the background so the user keeps their terminal; report the URL (http://localhost:5273). - The dev server reads the live datastore via its
/api/trackermiddleware — no copying needed. The user clicks ↻ Refresh after you log new applications with/rebound:track.
Notes
- Everything is local: the dashboard, the datastore, and all computed analytics stay on the user's machine.
- The private
situation(sponsorship/timeline) is intentionally not rendered. - To share a static snapshot:
npm run buildproducesdist/(but the built version reads bundled sample data, not the live datastore).
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 · 26 lines · 16 tokens per session scan A 1ff8c43a8830
dashboard is a command published in the GitHub repository snehag01/rebound (4 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 354 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
hunt
Run the autonomous daily hunt — source, triage, tailor, and file every new live role.
dashboard
Build a shareable HTML dashboard of your hunt — funnel, status, categories, recruiter scores — from the tracker.
tailor
Tailor an ATS-safe CV to one job description from the master profile.
cover-letter
Write a UK cover letter for a role, in the user's own voice.
setup
Scaffold a jobxhunter workspace and help register the job connectors (bring-your-own-keys).
intake
Build or update your master profile from the files in your workspace dump/ folder.