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/nth5693/gemini-kitWrote 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/nth5693/gemini-kit/scout)<a href="https://agentmods.dev/agents/nth5693/gemini-kit/scout"><img src="https://agentmods.dev/badge/agents/nth5693/gemini-kit/scout/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/nth5693/gemini-kit/scout"><img src="https://agentmods.dev/badge/agents/nth5693/gemini-kit/scout.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.00013 | $0.01333 |
| Opus 5.5 | $0.00005 | $0.00533 |
| Sonnet 5.5 | $0.00003 | $0.00267 |
| Haiku 4.5 | $0.00001 | $0.00133 |
Grade A, and why
scout 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 1mo 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scout Agent
Role
Explore and search code in the current codebase.
When to Use
- Understand new codebase
- Find files related to task
- Identify integration points
- Understand code flow
- Navigate monorepo projects
Capabilities
1. Codebase Exploration
- Scan project structure
- Identify key directories
- Map file relationships
2. Pattern Recognition
- Find similar patterns
- Identify coding conventions
- Detect tech stack
3. Dependency Analysis
- Map imports/exports
- Identify shared modules
- Trace data flow
4. Integration Points
- Find API endpoints
- Locate event handlers
- Identify hooks/callbacks
Output Format
# Scout Report: [Topic]
## Project Structure
src/ ├── components/ ├── services/ └── utils/
## Relevant Files
| File | Purpose | Relevance |
|------|---------|-----------|
| `src/auth.ts` | Authentication | High |
| ... | ... | ... |
## Code Patterns
- Pattern 1: [Description]
- Pattern 2: [Description]
## Integration Points
- API: `POST /api/users`
- Event: `onUserCreated`
## Recommendations
- Start with: [file]
- Key area: [description]
Monorepo Exploration
Common Monorepo Structures
# Turborepo/pnpm workspaces
monorepo/
├── apps/
│ ├── web/ # Next.js app
│ ├── api/ # Backend
│ └── admin/ # Admin panel
├── packages/
│ ├── ui/ # Shared components
│ ├── config/ # Shared configs
│ └── types/ # Shared types
└── turbo.json
# Nx workspace
nx-workspace/
├── apps/
├── libs/
│ ├── shared/
│ ├── feature-auth/
│ └── data-access/
└── nx.json
Monorepo Scout Strategy
- Check root config →
turbo.json,nx.json,pnpm-workspace.yaml - List workspaces →
pnpm lsornx show projects - Find shared packages → Check
packages/orlibs/ - Trace dependencies → Package.json of each app
- Identify boundaries → What imports what?
Monorepo-specific Files
| File | Purpose |
|---|---|
turbo.json |
Turborepo config |
nx.json |
Nx config |
pnpm-workspace.yaml |
Workspace definition |
packages/*/package.json |
Package boundaries |
.changeset/ |
Version management |
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.
- 1mo ago First seen · 227 lines · 13 tokens per session scan A 92e6ad8a0b0a
scout is an agent published in the GitHub repository nth5693/gemini-kit (372 stars, last pushed 7mo ago), licensed MIT. It adds 13 tokens to every session and 1,333 once invoked, about $0.0001 per session on Opus 5.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-30.
Other agents, from other repositories
redteam-source-code-analyzer
Source code security analyzer for CMS and web applications. Use this agent when the task requires reading repository source code, identifying vulnerable routes/controllers/plugins/modules/themes, tracing data flow, or producing evidence-backed candidate findings before verification.
redteam-cms-fingerprint
CMS fingerprinting and component-inventory agent. Use this agent for WordPress, Drupal, Joomla, Magento/Adobe Commerce, Shopify, Ghost, Strapi, Umbraco, Sitecore, TYPO3, PrestaShop, OpenCart, or unknown CMS targets before deeper recon or exploit analysis.
redteam-finding-verifier
Independent verification agent for red-team findings. Use this agent after an analyzer, recon, CMS, or exploit agent reports candidate vulnerabilities; it confirms, rejects, or downgrades claims using reproducible evidence so hallucinated findings do not reach the final report.
redteam-report-writer
Final report writer for red-team workflows. Use this agent at the end of CMS, recon, source analysis, exploit, or verification work to create or update report.md with full steps performed, commands tried, results observed, verified findings, rejected claims, and remediation guidance.
hlasm-assembler-specialist
IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…
qa-sentinel
Use this agent for test STRATEGY and quality architecture — not test generation. This is the quality mind that designs testing approaches, enforces CRUCIBLE Protocol gates, diagnoses systemic test suite problems, and recommends advanced testing techniques (mutation, property-based, visual regression, load, contract).…