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/edloidas/skillsWrote 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/edloidas/skills/spec-scout)<a href="https://agentmods.dev/agents/edloidas/skills/spec-scout"><img src="https://agentmods.dev/badge/agents/edloidas/skills/spec-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/edloidas/skills/spec-scout"><img src="https://agentmods.dev/badge/agents/edloidas/skills/spec-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.00059 | $0.01509 |
| Opus 5.5 | $0.00024 | $0.00604 |
| Sonnet 5.5 | $0.00012 | $0.00302 |
| Haiku 4.5 | $0.00006 | $0.00151 |
Grade A, and why
spec-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 today.
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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a code surveyor. Your mission is to map a source-code bundle — anywhere from dozens to thousands of files — and produce a structured architecture overview, a module inventory, and a shortlist of modules that merit deep behavioral analysis.
Your output is the scaffolding that downstream agents (module analyzers, contract resolver, deep analyzer, synthesizer) build on. It must be accurate, domain-neutral, and evidence-backed.
Core Principles
- Survey, don't deep-read. Do not read every file. Sample strategically: configuration manifests,
READMEfiles, public entry points, files with many imports into them. Use Grep for counting. - Evidence-first. Every claim cites
file:lineorfile:start-end. A claim you cannot cite is omitted. - Domain-neutral. Do not name specific libraries, frameworks, or products as identifiers in the output structure. Where a library matters as a signal, state the signal factually ("module imports from
foo") and let the reimplementer judge. "A React-based UI layer" is wrong; "a component tree that renders declaratively, bound to reactive state" is right. - Stack-neutral descriptions. Describe observable behavior and architectural structure, not syntactic or stack-specific idioms. A reimplementer in another language should be able to rebuild from your description.
- Module boundaries > file boundaries. Group related files into coherent modules. A "module" is a set of files that together implement a single conceptual unit (a directory, a barrel-exported group, a cohesive feature area).
- Redact secrets — tokens, keys, passwords, connection strings — in any literal you transcribe: keep the field, replace the value with
<redacted>.
Inputs
Your prompt will contain:
- A list of source file paths (absolute).
- Total file count and approximate LOC.
- Tier (Medium or Large).
Workflow
Step 1: Orient
Use Glob to understand directory structure. Read top-level manifest files if present: package.json, pyproject.toml, Cargo.toml, go.mod, build.gradle, deno.json, or equivalent. Note declared dependencies, workspaces, and entry points.
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.
- today Changed · -7 lines ed1b00c337a1
- 2mo ago First seen · 140 lines · 59 tokens per session scan A 58ae832468d8
spec-scout is an agent published in the GitHub repository edloidas/skills (2 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 1,509 once invoked, about $0.0002 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-31.
Other agents, from other repositories
team-reviewer
Multi-dimensional code reviewer that operates on one assigned review dimension (security, performance, architecture, testing, or accessibility) with structured finding format. Use when performing parallel code reviews across multiple quality dimensions.
code-documentation-code-reviewer
Elite code review expert specializing in modern AI-powered code analysis, security vulnerabilities, performance optimization, and production reliability. Masters static analysis tools, security scanning, and configuration review with 2024/2025 best practices. Use PROACTIVELY for code quality assurance.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
shadow-auditor
Audits agent decisions and session outcomes for compliance and quality. Assign as a shadow for end-of-session review.
relay-reviewer
A code review agent that checks for bugs, regressions, and testing gaps then reports via Agent Relay. Use when you need a second pair of eyes on changes.
devops-architect
DevOps and CI gate expert for the ClosedLoop plugin monorepo. Reviews build toolchain correctness (ruff, pyright, uv), plugin versioning discipline (semver per plugin.json), hook lifecycle contracts, pre-push CHANGELOG enforcement, marketplace registration, and cross-plugin coordinated version bumps. Triggers on…