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.
git clone --depth 1 https://github.com/pwdev-solucoes/pwdev-claude-marketplaceWrote 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/pwdev-solucoes/pwdev-claude-marketplace/customize)<a href="https://agentmods.dev/commands/pwdev-solucoes/pwdev-claude-marketplace/customize"><img src="https://agentmods.dev/badge/commands/pwdev-solucoes/pwdev-claude-marketplace/customize.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.1 | $0.00017 | $0.00675 |
| Opus 5 | $0.00009 | $0.00338 |
| Sonnet 5 | $0.00003 | $0.00135 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
customize 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pwdev-statusline:customize — Customize Status Line
Role
Customizes the status line via the configuration block at the top of
~/.claude/statusline.sh — every change is a 1-line edit of a config
variable, idempotent and reversible. Never comment out or restructure the
script body.
Input
$ARGUMENTS: the customization action.
Configuration block (top of the script)
SHOW_BRAND=1 SHOW_USER=1 SHOW_SESSION=1 SHOW_DIR=1 SHOW_MODEL=1
SHOW_GIT=1 SHOW_CTX=1 SHOW_TOKENS=1 SHOW_RATE=1
SEP=" | "
DIR_MAX_SEGMENTS=3
COLOR_BRAND / COLOR_USER / COLOR_SESSION / COLOR_DIR / COLOR_MODEL /
COLOR_GIT / COLOR_TOKENS (assigned from GREEN/BLUE/CYAN/MAGENTA/YELLOW/RED/WHITE)
Available Actions
show (default if no argument)
Read the config block and present: which sections are on/off (SHOW_), color assignments (COLOR_), separator, and DIR_MAX_SEGMENTS.
hide-<section> / show-<section>
Sections: brand, user, session, dir, model, git, ctx,
tokens, rate. Set the matching SHOW_<SECTION> variable to 0 or 1.
(One Edit; nothing else changes.)
colors
Present the current COLOR_* table, ask which section to recolor and to which
of the available colors, then reassign the variable (e.g.
COLOR_DIR="$CYAN"). Note: ctx and rate colors are dynamic
(green/yellow/red by threshold) and not configurable per-section.
separator <string>
Set SEP="<string>" (e.g. ·, ▸, —).
dir-depth <n>
Set DIR_MAX_SEGMENTS=<n> (0 = full path, N = keep last N segments with
…/ prefix).
Procedure
- Verify
~/.claude/statusline.shexists (else → suggest install). - Parse
$ARGUMENTS; apply the 1-line Edit to the config block only. - Preview the result:
echo '{"workspace":{"current_dir":"'$(pwd)'"},"model":{"display_name":"Fable 5"},"context_window":{"used_percentage":42,"total_input_tokens":100000,"total_output_tokens":5000},"rate_limits":{"five_hour":{"used_percentage":15}},"session_name":"demo"}' | bash ~/.claude/statusline.sh - Confirm the change was applied.
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 · 66 lines · 17 tokens per session scan A cd7654a43bf2
customize is a command published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 17 tokens to every session and 675 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-09-03.
Other commands, from other repositories
cancel-ralph
Cancel active Ralph Loop.
obsidian-recap
Summarize a time period from the vault - today, week, or month.
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement.
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.