pi-tools plugin
A set of extensions for the Pi agent: repository analysis, secrets leased with a TTL and search over agent sessions.
- 87 ★ on the repository
- Last commit
Extended access
Why this level
- Reads other agents' session transcripts on your disk and handles leased secrets
- Clones external repositories and can publish issues to Linear
Install
Manual install
pi install git:github.com/joelhooks/pi-toolsDependencies are installed beforehand by `setup.sh` from the repository; extensions are enabled through `pi config`.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Reads other agents' session transcripts on your disk and handles leased secrets
- Clones external repositories and can publish issues to Linear
This is third-party code. Review the repository files before installing.
What it does
pi-tools gathers extensions for the Pi coding agent. `repo-autopsy` clones GitHub repositories into `~/.repo-autopsy` and offers the `repo_clone`, `repo_structure`, `repo_search`, `repo_deps`, `repo_file` and `repo_find` tools. `secrets` leases secrets with a TTL through agent-secrets, shows status, revokes and keeps an audit. `session-reader` reads bounded slices of Pi, Claude, Codex, Cursor, Grok and OpenCode sessions when exact evidence is needed. Also included are `skill-shortcut` (a `$skill-name` autocomplete instead of `/skill:skill-name`), `aliases` (`/quit` and `/q` call `/exit`), `linear-tracker` (publishing issues to Linear under project policy with verified readback) and `shortlink-qr` for the author's short links and QR images. Each extension is enabled separately through `pi config`.
Who it is for. Pi users who need dependency analysis of other repositories, short-lived secrets and search over past agent sessions.
Good fit when
- Another repository must be cloned and its structure, dependencies and files inspected without manual work.
- An agent is given a secret for a limited time and it is then revoked.
- An exact quote from a past Claude, Codex or Cursor session must be found in the transcript.
- An issue description is published to Linear and the result must be checked by reading it back.
Not a fit when
- You do not use Pi: the extensions are written for that agent.
- General-purpose tools with no tie to the author's infrastructure are needed: some extensions, such as `shortlink-qr`, target his services.
- Secrets must live outside agent-secrets: the `secrets` extension works through it.
Example request
Clone the zod repository, show its structure and dependencies, then find the file defining the base schema.Limitations
The extensions target Pi and partly the author's personal infrastructure: `shortlink-qr` needs his short links, and the session memory service requires Executor, a token of at least 32 bytes and a macOS LaunchAgent. Dependencies are installed by `setup.sh` through `curl -sL .../setup.sh | bash`, and it should be read before running. `session-reader` reads other agents' transcripts from your disk, and secret leases need a separate agent-secrets. Extensions are toggled one by one through `pi config`.
How to disable. Disable the extensions in `pi config` or remove the package with Pi. Revoke leased secrets and delete `~/.repo-autopsy` by hand.
FAQ
How do I install it?
With `pi install git:github.com/joelhooks/pi-tools`, then enable what you need in `pi config`. Dependencies are installed by `setup.sh` from the repository.
Which tools does repo-autopsy have?
`repo_clone`, `repo_structure`, `repo_search`, `repo_deps`, `repo_file` and `repo_find`. Clones go into `~/.repo-autopsy` for reuse.
How do secrets work?
The `secrets` extension leases a secret with a TTL through agent-secrets, shows status, revokes and keeps an audit.
What does session-reader read?
Bounded fragments of Pi, Claude, Codex, Cursor, Grok and OpenCode sessions. The `session_context`, `session_inspect` and `session_chunks` tools work by session id or transcript path.
Are all extensions general-purpose?
No. `shortlink-qr` and the memory service target the author's personal services, while the other extensions apply more broadly.
Discussion
No questions or reviews yet.
Related
PluginsA build of the Pi coding agent with extensions: secret redaction, LSP, searchable context, telemetry, an event dashboard and team mode
A minimal terminal coding agent extended with skills, prompt templates and TypeScript packages
shitty-extensions adds fifteen extensions to the Pi agent: second opinions, plan mode, cost tracking and test loops.
Personal Pi agent setup with four commands for plan, todos, execution and review, passing state through Markdown session files.
A web app for the Pi coding agent: sessions survive restarts, teammates can join, and you can work from a phone with no cloud VM
Repeated pi agent steps accumulate as JavaScript programs with a manifest and tests, and pi calls them instead of redoing work.
README in short
Covers installation, the extension table, the `repo-autopsy` tools, `linear-tracker` rules and `session-reader` with its MCP integration.