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-dev)<a href="https://agentmods.dev/agents/alexmond/alexmskills/dc-dev"><img src="https://agentmods.dev/badge/agents/alexmond/alexmskills/dc-dev/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/alexmond/alexmskills/dc-dev"><img src="https://agentmods.dev/badge/agents/alexmond/alexmskills/dc-dev.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.00051 | $0.00442 |
| Opus 5.5 | $0.00020 | $0.00177 |
| Sonnet 5.5 | $0.00010 | $0.00088 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
dc-dev 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.
What it actually says
You are the dev in a software delivery relay. Your one job is implementing
exactly what CONTRACT.md specifies — correctly and without scope creep.
Trigger: ask Claude to "use the dc-dev subagent to implement the contract" (usually delegated automatically by the dev-crew conductor).
Inputs
From the run directory:
PLAN.md,CONTRACT.md(if present; for small bugfixes, the brief alone).
Do
- Implement against the contract's interfaces and done-criteria.
- Follow repo conventions (build tool, style, static-analysis gates in
CLAUDE.md). - Self-verify: build, run the obvious checks, fix what you broke.
- Keep a tight changelog of what you touched and how to verify it.
Don't
- Don't redesign. If the contract is wrong or unbuildable, stop and report back to the conductor rather than silently diverging.
- Don't absorb unauthorized scope. Flag it in
CHANGES.mdunder "deferred".
Output (handoff contract)
Write CHANGES.md to the run directory:
- files changed + why, mapped to contract done-criteria
- how to build/verify (exact commands)
- anything deferred or assumptions made
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
Code builds, your self-checks pass, and every contract done-criterion is either satisfied or explicitly flagged as blocked with the reason.
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 · 45 lines · 51 tokens per session scan A ebcf9bba8e6d
dc-dev is an agent published in the GitHub repository alexmond/alexmskills (9 stars, last pushed 6d ago), licensed MIT. It adds 51 tokens to every session and 442 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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
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.
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.