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/fiale-plus/fiale-claude-plugins/hub-setupgit clone --depth 1 https://github.com/fiale-plus/fiale-claude-pluginsWrote 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/fiale-plus/fiale-claude-plugins/hub-setup)<a href="https://agentmods.dev/commands/fiale-plus/fiale-claude-plugins/hub-setup"><img src="https://agentmods.dev/badge/commands/fiale-plus/fiale-claude-plugins/hub-setup.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.00010 | $0.00991 |
| Opus 5 | $0.00005 | $0.00495 |
| Sonnet 5 | $0.00002 | $0.00198 |
| Haiku 4.5 | $0.00001 | $0.00099 |
Grade B, and why
hub-setup 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 4d 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.
Update `~/.claude/settings.json`: 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.
Hub Setup
Configure Claude Code to use Status Hub's statusline.
Step 1: Parse Arguments
Check if --replace flag was provided.
Step 2: Preserve Existing Statusline
If NOT --replace, save existing statusline to ~/.claude/status-base-config.json:
statusLine.type == "command": save{ "type": "command", "value": "<path>" }statusLine.type == "text": save{ "type": "text", "value": "<text>" }- No statusLine: detect shell prompt or use
{ "type": "default" }
If --replace: save { "type": "default" }.
Step 3: Update Settings
Update ~/.claude/settings.json:
{
"statusLine": {
"type": "command",
"command": "${CLAUDE_PLUGIN_ROOT}/bin/statusline.sh"
}
}
Step 4: Add Permissions
Add to permissions.allow (expand all variables to actual paths):
Read(${HOME}/.claude/status-config.json)
Write(${HOME}/.claude/status-config.json)
Read(${HOME}/.claude/status-base-config.json)
Read(/tmp/status-hub.json)
Write(/tmp/status-hub.json)
Read(${CLAUDE_PLUGIN_ROOT}/skills/*)
Read(${CLAUDE_PLUGIN_ROOT}/bin/*)
Bash(gh pr view:*)
Bash(${CLAUDE_PLUGIN_ROOT}/bin/update-bridge.sh *)
mcp__claude-in-chrome__javascript_tool
mcp__claude-in-chrome__tabs_context_mcp
Merge with existing permissions (deduplicate).
Step 5: Initialize Config Files
Status Config (~/.claude/status-config.json)
- If missing: create
{"background": null, "foreground": []} - If corrupt: restore from
.bakor create fresh - If exists: migrate schema (add contextDisplay, calendar if missing)
- Always backup before modifying
Bridge File (/tmp/status-hub.json)
Create: {"timestamp": null, "background": null, "foreground": []}
Legacy Daemon Cleanup
If /tmp/status-hub-daemon.lock contains old format (just PID, no VERSION:):
kill -9 <pid>and remove lockfile- New daemon spawns via SessionStart hook
Step 6: Configure Calendar (Optional)
Detect available methods, then present consolidated wizard:
{
"question": "Enable Google Calendar meeting alerts?",
"header": "Calendar",
"options": [
{"label": "Chrome browser tab", "description": "<dynamic status>"},
{"label": "Playwright (headless)", "description": "<dynamic status>"},
{"label": "Skip for now", "description": "Configure later with /hub-setup-gcalendar"}
]
}
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.
- 4d ago First seen · 140 lines · 10 tokens per session scan B e40c739fd685
hub-setup is a command published in the GitHub repository fiale-plus/fiale-claude-plugins (4 stars, last pushed 4mo ago), licensed MIT. It adds 10 tokens to every session and 991 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
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
statusbar-theme
Switch the status-bar color theme (graphite / twilight / linen).
statusbar-preview
Render every style × theme combination using your real cached data.
statusbar-reset
Wipe the status-bar config back to defaults.
statusbar-doctor
Run cs doctor to diagnose why the status bar isn't showing what you expect.
statusbar
Show current status-bar config and list available styles + themes.