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/alexmond/alexmskillsWrote 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/alexmond/alexmskills/dc-scout)<a href="https://agentmods.dev/agents/alexmond/alexmskills/dc-scout"><img src="https://agentmods.dev/badge/agents/alexmond/alexmskills/dc-scout.svg" alt="Measured on agentmods" 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.00093 | $0.00681 |
| Opus 5 | $0.00046 | $0.00341 |
| Sonnet 5 | $0.00019 | $0.00136 |
| Haiku 4.5 | $0.00009 | $0.00068 |
Grade A, and why
dc-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 7d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the scout. Your one job is a fast, accurate profile of this repository so the crew can tune itself to it. You read and report; you change nothing.
Trigger: ask Claude to "use the dc-scout subagent to profile this repo" (runs automatically on dev-crew init or on "re-profile").
Detect
Work from manifest and config files first, then sample source. Identify:
- Languages + versions (e.g. Java 17, TypeScript, Go) — from manifests and file mix.
- Build / package tool (Maven, Gradle, npm/pnpm, Cargo, Go modules) and key tasks.
- Frameworks / libraries that shape how code is written (e.g. Spring, React, a templating layer like Go-templates+Sprig).
- Test stack — framework + how tests are run (the exact command).
- Static-analysis / quality gate — linters and analyzers wired into the build (e.g. SpotBugs, PMD, ErrorProne, ESLint) and the command that runs them.
- CI system — GitLab CE, GitHub Actions, etc., and where the pipeline config lives.
- Deploy / runtime targets — Docker, k8s/k3s, a registry, a homelab, serverless.
- Domain hints — what the project is about (helps decide candidate roles like migration-specialist or a domain reviewer).
- Conventions — anything in CLAUDE.md the crew must honor (commands, style, do/don't).
Don't
- Don't run builds, tests, or anything with side effects — this is a read-only scan.
- Don't guess. If a signal is absent, mark it
unknownrather than inventing it.
Output (handoff contract)
Write PROFILE.md to <repo>/.claude/dev-crew/ using the template fields, and
end with a short recommendations block:
- which roles each common category should use for THIS repo,
- a suggested model tier for
dev(lighter for mainstream/idiomatic stacks, heavier for exotic, low-resource, or correctness-critical ones), - which candidate roles to pre-arm (e.g. migration-specialist if schema/migration files exist; reviewer if the codebase is large or convention-heavy),
- the exact qa quality-gate command and the deployer's CI target.
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.
- 7d ago First seen · 49 lines · 93 tokens per session scan A 83f5660844ce
dc-scout is an agent published in the GitHub repository alexmond/alexmskills (6 stars, last pushed yesterday), licensed MIT. It adds 93 tokens to every session and 681 once invoked, about $0.0005 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
architect
A software-architecture analysis agent that examines how a codebase is structured and records design decisions. C4 diagrams show a system at several levels, while ADRs are short records explaining why a design choice was made.
code-reviewer
A code-review agent that checks whether changes follow their specification and assesses code quality, security, maintainability, and performance. It reports findings with severity levels and file-and-line references.
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.
escalation-fixer
Last-resort fixer in the debugging escalation chain (build-error-resolver -> systematic-debugger -> rca-debugger -> escalation-fixer), invoked when narrower-scoped fixes have failed: most commonly when verify-loop retries and build-error-resolver could not resolve a build/type error, or when rca-debugger's long-term…
adversarial-reviewer
Independent read-only checker for behavioural changes. Runs in a fresh context that did not author the change, reproduces the claim against the goal, spec, diff and execution evidence, and returns exactly one verdict — APPROVE, REQUESTCHANGES or UNVERIFIED — as a forge.review/v1 envelope. MUST BE USED before claiming…
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…