shell-init

Shell integration setup that prints code for connecting PAI commands to your shell, such as zsh.

In plain words
What is it for?
Run it and add its output to your zsh configuration file with eval so the shell integration loads in new sessions.
Why use it?
It provides the shell configuration needed for the integration to work from your terminal.

Command

Install

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.

agentmods
npx agentmods add commands/mnott/pai/shell-init
Clone the repo
git clone --depth 1 https://github.com/mnott/PAI
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 301 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 83% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00301
Opus 5 $0.00000 $0.00151
Sonnet 5 $0.00000 $0.00060
Haiku 4.5 $0.00000 $0.00030

Measured 2d ago against content hash bfd3d6085603, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

shell-init 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 2d 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.

Origin

This is a copy

83% identical to backup — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

docs/commands/shell-init.md · 19 lines

What it actually says

pai shell-init

Emit shell integration code. Add to ~/.zshrc: eval "$(pai shell-init)"

Synopsis

pai shell-init

See also

pai backup · pai clear-names · pai daemon · pai db · pai end · pai help · pai identity · pai kg · pai mcp · pai memory · pai notify · pai observation · pai obsidian · pai pause · pai project · pai projects · pai registry · pai restore · pai session · pai sessions · pai setup · pai skill · pai task · pai topic · pai update · pai zettel

Run pai help <area> to read any of these in the terminal.

Changes

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.

  1. 2d ago First seen · 19 lines · 0 tokens per session scan A bfd3d6085603

Subscribe to this mod's changes

shell-init is a command published in the GitHub repository mnott/PAI (45 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 301 tokens. A static security scan graded it A with 0 findings. It is 83% identical to backup, differing in 14 lines, and is treated as a copy.