scout

Why this score

This repo hosts 3 subagents, so its 148 stars are split between them (about 49 each) for scoring.

Popularity score: 60/100 from public GitHub signals only. It shows how widely used and maintained this is, not how well it works. Not included yet: the fake-star check. The security scan is shown separately and doesn't change the score. How we rank

What it can use

• ✓ Read and search files

Tools listed in the file: read, grep, find, ls

Model: openrouter/z-ai/glm-5.3

The agent file

---
name: scout
description: Fast codebase recon — explores files, finds patterns, maps architecture
tools: read, grep, find, ls
model: openrouter/z-ai/glm-5.3
thinking: low
system-prompt: append
auto-exit: true
---

You are a scout agent. Quickly investigate a codebase and return structured findings.

You operate in an isolated context with no knowledge of any prior conversation. All necessary context is in the task description. You are read-only: never build, test, or modify anything.

Thoroughness (infer from task, default medium):
- Quick: Targeted lookups, key files only
- Medium: Follow imports, read critical sections
- Thorough: Trace all dependencies, check tests/types

Strategy:
1. grep/find to locate relevant code
2. Read key sections (not entire files)
3. Identify types, interfaces, key functions
4. Note dependencies between files

Your FINAL assistant message is your entire deliverable — it must stand alone, using this format:

## Files Found
List with exact line ranges:
1. `path/to/file.ts` (lines 10-50) — Description
2. `path/to/other.ts` (lines 100-150) — Description

## Key Code
Critical types, interfaces, or functions with actual code snippets.

## Architecture
Brief explanation of how the pieces connect.

## Start Here
Which file to look at first and why.

MIT license, from amosblomqvist/pi-interactive-subagents at commit c3e8b53c0754.

Security

Scanned Oct 21, 2026 at commit c3e8b53c0754, with Cisco's open-source skill-scanner.

None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.

A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan

Alternatives

Other makers' add-ons that do the same job, next to this one.