Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ihudak/ihudak-claude-plugins/plugin install workflows-coreWrote 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/ihudak/ihudak-claude-plugins/statusline)<a href="https://agentmods.dev/commands/ihudak/ihudak-claude-plugins/statusline"><img src="https://agentmods.dev/badge/commands/ihudak/ihudak-claude-plugins/statusline/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/ihudak/ihudak-claude-plugins/statusline"><img src="https://agentmods.dev/badge/commands/ihudak/ihudak-claude-plugins/statusline.svg" alt="Reviewed on agentmods" width="80" 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.00063 | $0.00829 |
| Opus 5.5 | $0.00025 | $0.00332 |
| Sonnet 5.5 | $0.00013 | $0.00166 |
| Haiku 4.5 | $0.00006 | $0.00083 |
Grade B, and why
statusline 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 23d 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.
line and wires it into `~/.claude/settings.json`. The shipped script also How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Install the plugin family's status line: $ARGUMENTS
/workflows-core:statusline installs the plugin's multi-line, truecolor status
line and wires it into ~/.claude/settings.json. The shipped script also
writes the per-session cost snapshot that enables Option B of session cost
reporting (see ${CLAUDE_PLUGIN_ROOT}/references/cost-emission.md §5).
Installation is idempotent and backs up anything it would overwrite.
This is the only change the command makes; it changes no workflow-command
behavior.
Note: Claude Code ships its own built-in /statusline command (backed by the
statusline-setup agent), so the bare /statusline resolves to Claude Code's
built-in flow. This is one instance of the general rule — see rule 6 of
${CLAUDE_PLUGIN_ROOT}/references/next-phase-offer.md: printed command names
are always fully qualified. Direct users to /workflows-core:statusline.
Phase 1 — Resolve paths
- Source script:
${CLAUDE_PLUGIN_ROOT}/scripts/statusline-command.sh. - Stable install path:
~/.claude/dev-workflows/statusline-command.sh(per-user, survives plugin re-installs). Create~/.claude/dev-workflows/if missing. - Settings file:
~/.claude/settings.json.
Phase 2 — Preflight & back up
- Read
~/.claude/settings.json(treat a missing file as{}). - If a
statusLineblock already exists, print it and back it up to~/.claude/settings.json.dev-workflows.bak(do NOT overwrite an existing backup — suffix-2,-3, … ). - If
~/.claude/dev-workflows/statusline-command.shalready exists, back it up the same way (.bak, then-2, … ) before overwriting. - Verify
bashandjqare available; ifjqis missing, do the Phase 4 JSON merge withpython3instead — never hand-editsettings.jsonblindly.
Phase 3 — Install the script
Copy the source script to the stable install path and chmod +x it. Verify it is
non-empty and begins with a #! shebang.
Phase 4 — Merge the settings block (confirm first)
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.
- 23d ago Changed · -1 tokens per session 24085fb4e0fc
- 1mo ago Changed 7d7dfadce583
- 1mo ago First seen · 74 lines · 64 tokens per session scan B 329279c50c88
statusline is a command published in the GitHub repository ihudak/ihudak-claude-plugins (2 stars, last pushed 24d ago), licensed MIT. It adds 63 tokens to every session and 829 once invoked, about $0.0003 per session on Opus 5.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-09-05.
Other commands, from other repositories
acos-checkpoint
Create checkpoints before risky operations. Rollback if things go wrong.
cleanup-branches
Delete merged branches and flag stale unmerged branches for cleanup.
create-pr
Context-aware GitHub Pull Request creation and update assistant.
merge
You are executing the /hydra:merge command. Merge a worktree branch back into the current branch.
instinct-import
Import a portable YAML instinct pack with confidence-gated merge (Instinct Engine).
check-fix
Execute quality gates, fix any issues found, and create a single high-quality Conventional Commit summarizing all changes made.