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-contextgit 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-context)<a href="https://agentmods.dev/commands/fiale-plus/fiale-claude-plugins/hub-context"><img src="https://agentmods.dev/badge/commands/fiale-plus/fiale-claude-plugins/hub-context.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.00414 |
| Opus 5 | $0.00005 | $0.00207 |
| Sonnet 5 | $0.00002 | $0.00083 |
| Haiku 4.5 | $0.00001 | $0.00041 |
Grade A, and why
hub-context 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.
What it actually says
/hub-context - Context Window Display Setup
Configure how context window usage is displayed in your statusline.
Process
Step 1: Ask Display Format
Use AskUserQuestion:
question: "How should context usage be displayed?"
header: "Format"
options:
- label: "Bar [████░░ 42%]"
description: "Visual progress bar with percentage"
- label: "Percent only"
description: "Just show 42%"
- label: "Threshold alert"
description: "Hidden until above threshold, then show warning"
Map answers:
- "Bar" →
contextDisplay: "bar" - "Percent only" →
contextDisplay: "percent" - "Threshold alert" →
contextDisplay: "threshold"
Step 2: Ask Alert Threshold
Use AskUserQuestion:
question: "Alert when context usage exceeds?"
header: "Threshold"
options:
- label: "60%"
- label: "70%"
- label: "80% (Recommended)"
- label: "90%"
Step 3: Save Configuration
Read ~/.claude/status-config.json and update:
{
"contextDisplay": "bar",
"contextAlertThreshold": 80,
...existing config...
}
Step 4: Confirm
Say:
Context display configured!
Format: <bar/percent/threshold>
Alert threshold: <X>%
Your statusline will now show context usage after the git branch.
Example: main* [████░░░░░░ 42%] › ▶ Song › 2 PRs >
Colors:
- Green: <60% used
- Yellow: 60-80% used
- Red: >80% used (alert state)
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 · 78 lines · 10 tokens per session scan A fa328de9e571
hub-context 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 414 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
post-task
Execute post-task cleanup, performance analysis, and memory storage.
architect
System design with Memory-based coordination for scalable architectures.
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.
grill-me
Run an interactive one-question-at-a-time oral drill for research defence or active-recall study, escalating around weak answers and ending with a study sheet. Use when the user asks to be grilled, quizzed, or prepared for a viva, job talk, seminar, or exam. Not for a written critique; use $devils-advocate or a review…
thoughts_init
Initialize thoughts system for current repository.