Borrowing it
Nothing to install: this file belongs to vlad-ryzhkov/ai-context-engineering-for-qa. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vlad-ryzhkov/ai-context-engineering-for-qa/main/.claude/skills/repo-scout/SKILL.mdgit clone --depth 1 https://github.com/vlad-ryzhkov/ai-context-engineering-for-qaWrote 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/skills/vlad-ryzhkov/ai-context-engineering-for-qa/repo-scout)<a href="https://agentmods.dev/skills/vlad-ryzhkov/ai-context-engineering-for-qa/repo-scout"><img src="https://agentmods.dev/badge/skills/vlad-ryzhkov/ai-context-engineering-for-qa/repo-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/skills/vlad-ryzhkov/ai-context-engineering-for-qa/repo-scout"><img src="https://agentmods.dev/badge/skills/vlad-ryzhkov/ai-context-engineering-for-qa/repo-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.00064 | $0.06983 |
| Opus 5 | $0.00032 | $0.03492 |
| Sonnet 5 | $0.00013 | $0.01397 |
| Haiku 4.5 | $0.00006 | $0.00698 |
Grade A, and why
repo-scout scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Grep HTTP client init: `http.NewRequest`, `resty.New()`, `axios.create`, `WebClient.builder()` How it starts
The opening of the file, as written. The whole thing — 517 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/repo-scout — Backend Repository Reconnaissance
Scope (SINGLE AUTHORITY)
repo-scout is the ONLY skill responsible for initial repository discovery.
- It reads, catalogs, and extracts business logic facts (validations, errors, auth flows).
- It detects entity dependencies, state machines, behavioral nuances, resilience patterns, and produces a Test Generation Blueprint for downstream skills.
- It NEVER evaluates code quality, suggests improvements, or generates test code.
- It NEVER generates test files or execution plans.
Out of Scope (NEVER do these):
- Architecture pattern detection or diagram generation (MVC, Hexagonal, etc.) — irrelevant for test planning
- Code quality evaluation or improvement suggestions (existing constraint — restated for clarity)
- Execution of external scripts or dependency installation (
pip install,npm install, etc.)
When to Use
- First entry into a new backend repository
- Before
/api-isolated-tests— for data collection - Before
/init-project— to understand the target service - Periodic audit: "what changed in the API surface?"
When NOT to Use
- QA projects with tests (use
/init-project) - Code review (use standard tools)
- Frontend/mobile repositories
Analysis Anti-Patterns (NEVER DO)
| Anti-Pattern | Why Skipped |
|---|---|
| Line count (cloc) | Useless metric for QA — number of routes and hierarchy depth matter |
| Cyclomatic complexity | Parsing linter JSON in bash is fragile; delegate to SonarQube/CI |
| Architecture pattern detection (MVC, DDD, Clean, Hexagonal) | Folder naming is irrelevant — routes and DB schema are what matter |
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago Changed · +496 lines · +33 tokens per session e9d1bffb60ca
- 11d ago First seen · 21 lines · 31 tokens per session scan A 72f269d41cc9
repo-scout is a skill published in the GitHub repository vlad-ryzhkov/ai-context-engineering-for-qa (6 stars, last pushed 2d ago), licensed Unlicense. It adds 64 tokens to every session and 6,983 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
detecting-broken-object-property-level-authorization
Detect and test for OWASP API3:2023 Broken Object Property Level Authorization vulnerabilities including excessive data exposure and mass assignment attacks.
voiden
Create and edit Voiden .void files for API testing. Covers the .void file format and all enabled extension block types.
detecting-api-enumeration-attacks
Detect and prevent API enumeration attacks including BOLA and IDOR exploitation by monitoring sequential identifier access patterns and authorization failures.
performing-api-inventory-and-discovery
Performs API inventory and discovery to identify all API endpoints in an organization's environment including documented, undocumented, shadow, zombie, and deprecated APIs. The tester uses passive traffic analysis, active scanning, DNS enumeration, JavaScript analysis, and cloud resource inventory to build a…
magpie-release-promote
Emit the backend-shaped promotion command set for a release that has passed its vote. Reads the planning issue (must carry vote-passed), constructs the staging → release move for the configured distribution backend, checks PMC membership of the Release Manager, and proposes the promoted label. Never runs the promotion…
backendless-automation
Automate Backendless tasks via Rube MCP (Composio). Always search tools first for current schemas.