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/shivaedev/pardes/statusline-setupgit clone --depth 1 https://github.com/ShivaeDev/pardesWhat 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.00052 | $0.00422 |
| Opus 5 | $0.00026 | $0.00211 |
| Sonnet 5 | $0.00010 | $0.00084 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade B, and why
statusline-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 yesterday.
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.
Run the plugin's setup in force mode. This refreshes the stable launcher at `~/.claude/statusline-pardes.sh` so it points at the current plugin source, then points `~/.claude/settings.json`'s `statusLine` at that launche What it actually says
statusline-setup
Explicitly install or refresh the main status line for the statusline plugin.
The subagent status line is wired automatically (it ships in the plugin's bundled settings.json). The main line cannot be set declaratively by a plugin, so it is wired by a SessionStart hook — and by this command, for an on-demand (re)install.
What to do
Run the plugin's setup in force mode. This refreshes the stable launcher at ~/.claude/statusline-pardes.sh so it points at the current plugin source, then points ~/.claude/settings.json's statusLine at that launcher:
STATUSLINE_PARDES_FORCE=1 "${CLAUDE_PLUGIN_ROOT}/hooks/session-start.sh"
Then report the outcome to the user based on what the script printed:
- Wired / refreshed — the main status line now renders via this plugin. Tell the user it is active. It takes effect on the next status-line refresh; a new session guarantees it.
- Custom status line left untouched — the user already has their own
statusLinecommand insettings.json. The plugin will NOT overwrite it. To switch, tell the user to remove the existingstatusLinekey from~/.claude/settings.json, then run/statusline-setupagain.
How to revert
Tell the user they can remove the wiring at any time by deleting the "statusLine" key from ~/.claude/settings.json. The launcher file ~/.claude/statusline-pardes.sh is harmless to leave or delete; it is recreated whenever the plugin is active and a session starts.
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.
- yesterday First seen · 29 lines · 52 tokens per session scan B e34a7ebb5943
statusline-setup is a command published in the GitHub repository ShivaeDev/pardes (5 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 422 once invoked, about $0.0003 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.