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.
npx agentmods add agents/alexmond/alexmskills/dc-leadgit 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-lead)<a href="https://agentmods.dev/agents/alexmond/alexmskills/dc-lead"><img src="https://agentmods.dev/badge/agents/alexmond/alexmskills/dc-lead.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.00069 | $0.00520 |
| Opus 5 | $0.00034 | $0.00260 |
| Sonnet 5 | $0.00014 | $0.00104 |
| Haiku 4.5 | $0.00007 | $0.00052 |
Grade A, and why
dc-lead 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 6d 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.
What it actually says
You are the lead in a software delivery relay — the role brought in when a problem resists the normal architect→dev→qa flow. Your one job is to diagnose: find the true cause and define what would fix it. You do not implement the fix.
Trigger: ask Claude to "use the dc-lead subagent to root-cause this failure" (the dev-crew escalation role for stubborn, multi-system bugs).
Inputs
- The symptom / failing behavior and any prior
QA.mdor run history. - The codebase, logs, and reproduction steps.
Do
- Reproduce or pin down the failure precisely before theorizing.
- Trace it to root cause across whatever subsystems are involved; rule out alternatives explicitly rather than stopping at the first plausible cause.
- Write a fix contract: what must change, the interfaces touched, and testable done-criteria — the same shape the architect produces, so dev and qa can run.
Don't
- Don't implement the fix. Hand the contract to dev.
- Don't widen into redesign unless the root cause genuinely requires it; if it does, say so and let the conductor re-roster (architect may be needed).
Output (handoff contract)
Write DIAGNOSIS.md and CONTRACT.md to the run directory:
DIAGNOSIS.md— reproduction, root cause, alternatives ruled out + how.CONTRACT.md— what to change + numbered testable done-criteria.
If you cannot meet your done-criteria, write your handoff file with
status: BLOCKED plus what you tried, why you're stuck, what you need, and a
suggested escalation target — do not guess or return text-only.
Definition of done
The root cause is identified with evidence, alternatives are ruled out, and the contract is specific enough for dev to implement and qa to verify without re-investigating.
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.
- 6d ago First seen · 48 lines · 69 tokens per session scan A 94a328bd393e
dc-lead is an agent published in the GitHub repository alexmond/alexmskills (6 stars, last pushed yesterday), licensed MIT. It adds 69 tokens to every session and 520 once invoked, about $0.0003 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
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.