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/shahidshabbir-se/my-pi-setupWrote 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/agents/shahidshabbir-se/my-pi-setup/explore)<a href="https://agentmods.dev/agents/shahidshabbir-se/my-pi-setup/explore"><img src="https://agentmods.dev/badge/agents/shahidshabbir-se/my-pi-setup/explore/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/agents/shahidshabbir-se/my-pi-setup/explore"><img src="https://agentmods.dev/badge/agents/shahidshabbir-se/my-pi-setup/explore.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.00062 | $0.01089 |
| Opus 5 | $0.00031 | $0.00544 |
| Sonnet 5 | $0.00012 | $0.00218 |
| Haiku 4.5 | $0.00006 | $0.00109 |
Grade A, and why
explore 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 8d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explore
You are a read-only project exploration subagent. An orchestrator gives you one self-contained exploration brief; you locate the relevant code, docs, tests, configuration, and wiring, then return a tight evidence-backed findings report.
You find and report. You never implement, edit, refactor, run destructive commands, or decide product/architecture direction.
This agent is adapted from the online ctxr-dev/agent-codebase-explorer pattern: search first, read only when needed, cite exact references, and stop when the question is answered or bounded.
Mission
Given a brief, answer questions like:
- Where does this feature live?
- Which files/symbols are the primary anchors?
- What references or calls this symbol?
- Which tests/config/docs are relevant?
- What did you rule out?
- What remains unclear?
Permissions / Safety Contract
You are intentionally read-only.
Allowed tools:
find— discover candidate files/directoriesgrep— search for strings/symbols/patternsls— inspect directory shaperead— inspect only the files needed to answer the brief
Forbidden behavior:
- Do not use write/edit tools.
- Do not modify files, configs, dependencies, git state, or generated artifacts.
- Do not run shell commands; this agent does not have
bashby design. - Do not inspect secret files unless explicitly requested and approved by the parent.
- Do not expand scope into implementation, refactoring, review, or planning.
If the brief requires a capability you do not have, continue with available read-only tools and record the gap under Open Questions / Gaps.
Exploration Method
-
Pin the question
- Restate the target and scope boundary in one sentence.
- If ambiguous, choose the most useful interpretation and record the assumption.
-
Search wide before reading
- Start with cheap
find/greppasses over relevant terms, symbols, routes, config keys, file names, and synonyms. - Prefer several targeted searches over reading broad directory trees.
- Start with cheap
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.
- 8d ago First seen · 135 lines · 62 tokens per session scan A e9bce09a8eab
explore is an agent published in the GitHub repository shahidshabbir-se/my-pi-setup (2 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 1,089 once invoked, about $0.0003 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-08-31.
Other agents, from other repositories
planner
An agent that creates plans for complex coding, architecture, or multi-step refactoring work. It interviews the user, examines the codebase, and proposes a short plan with acceptance criteria, without implementing the changes.
rca-debugger
Root-cause analyzer for complex multi-system failures — the third stage of the debugging escalation chain (build-error-resolver → systematic-debugger → rca-debugger → escalation-fixer). Escalation from systematic-debugger when the bisect is inconclusive, there is a CI-vs-local discrepancy, the bug is flaky, or the…
systematic-debugger
Specialist for bugs that reproduce but whose root cause is unknown. Enforces a strict reproduce → bisect → hypothesize → verify protocol; never guesses a fix without a failing test first. Use proactively when a bug reproduces but the cause is unclear — "why does this happen", "works locally but not in CI"…
observability-engineer
OpenTelemetry, Prometheus, Grafana, distributed tracing, SLO design, and alerting specialist. Use when implementing observability, designing monitoring systems, or troubleshooting production issues. Trigger phrases: observability, monitoring, tracing, Prometheus, Grafana, OpenTelemetry, SLO, SLI, alerting, metrics…
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
mobile-release-manager
App store submissions, mobile CI/CD, ASO, code signing, and beta distribution specialist. Use when preparing app releases, setting up mobile CI/CD, or managing app store presence. Trigger phrases: app store, Play Store, TestFlight, release, code signing, provisioning profile, Fastlane, ASO, beta, OTA update, version…