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-treegit 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-tree)<a href="https://agentmods.dev/commands/fiale-plus/fiale-claude-plugins/hub-tree"><img src="https://agentmods.dev/badge/commands/fiale-plus/fiale-claude-plugins/hub-tree.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.00685 |
| Opus 5 | $0.00005 | $0.00342 |
| Sonnet 5 | $0.00002 | $0.00137 |
| Haiku 4.5 | $0.00001 | $0.00068 |
Grade A, and why
hub-tree 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 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.
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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hub List - Tree View
Display all tracked items in a tree format with numbered references.
Process
- Read
~/.claude/status-config.json - If file doesn't exist or empty, say "No items being tracked. Use
/hub <service>or/hub <pr-url>to start." - Build tree output:
Status Hub
│
├─ STATUSLINE
│ ├─ Context: bar [████░░░░░░ 42%] threshold 80%
│ └─ Quota: bar [██░░░░░░░░ 18%] threshold 80% (Max 5hrs)
│
├─ FOREGROUND
│ ├─ #1 PR #17163 [icon] [state] [detail] [NEW]
│ ├─ #2 PR #17042 [icon] [state] [detail]
│ └─ #3 PR #16998 [icon] [state] [detail]
│
└─ BACKGROUND
└─ #4 [icon] [service]: [title] - [detail]
Tip: /hub ack #1 | /hub-manage
Statusline Settings
Read from config and display current settings:
contextDisplay: "bar" | "percent" | "threshold" | (not set = off)contextAlertThreshold: number (default 80)quota.displayFormat: "bar" | "number" | "compact" | "off" | (not set = off)quota.alertThreshold: number (default 80)quota.plan: "pro" | "max5" | "max20" | "custom"
Show current usage from /tmp/status-hub-quota.json if available.
Display format:
- If context enabled:
Context: <format> [<visual>] threshold <N>% - If context off:
Context: off - If quota enabled:
Quota: <format> [<visual>] threshold <N>% (<plan>) - If quota off:
Quota: off (tracking silently)
Foreground Items
For each PR in config.foreground:
- Refresh status via
gh pr view - Compare to
lastSeenstate - Mark as
[NEW]if:- Comments increased
- State changed
- Review decision changed
- Checks status changed
- Display:
#N PR #<number> <icon> <state> <detail>
Background Item
If config.background exists:
- Get current status from browser tab (if available)
- Display:
#N <icon> <service>: <title> - <detail>
Icons
| Icon | Meaning |
|---|---|
| > | Playing |
| || | Paused |
| M | Mail/Gmail |
| ✓ | PR Approved |
| ? | PR Review needed |
| ! | Changes requested |
| X | Checks failing |
| ~ | Checks pending |
| D | Draft |
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 · 82 lines · 10 tokens per session scan A 8e1d7ac0f46b
hub-tree 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 685 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
paul:add-phase
Add a new phase to current milestone.
workflow-design
Exécuter la phase de Conception (Solutioning) - spécification technique et architecture.
sprint
Équipe de Développement Sprint - Implémentation parallèle de stories utilisant les Agent Teams.
daily-standup
Génération Résumé Daily Stand-up.
speckit.companion.implement
Companion implement — execute tasks.md in dependency order, then mark complete.
speckit.companion.living-move
Move a living spec between central and colocated storage — file, tiers, and registry together (opt-in, reversible).