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 skills/realdougeubanks/claudemarketplace/agent-based-developmentnpx skills add RealDougEubanks/ClaudeMarketplace --skill agent-based-developmentgit clone --depth 1 https://github.com/RealDougEubanks/ClaudeMarketplaceWrote 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/realdougeubanks/claudemarketplace/agent-based-development)<a href="https://agentmods.dev/skills/realdougeubanks/claudemarketplace/agent-based-development"><img src="https://agentmods.dev/badge/skills/realdougeubanks/claudemarketplace/agent-based-development.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.00034 | $0.00965 |
| Opus 5 | $0.00017 | $0.00483 |
| Sonnet 5 | $0.00007 | $0.00193 |
| Haiku 4.5 | $0.00003 | $0.00097 |
Grade A, and why
agent-based-development 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 5d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent-Based Development — Async Multi-Agent Workflow
Run a full async multi-agent software development workflow using file-based artifact handoffs. Each invocation adopts a specific agent role and operates according to that role's responsibilities.
This is the orchestrator skill. Identify your single assigned role first (from the slash command used or the latest plan artifact), then follow that role's skill. Do not attempt to act as multiple roles in one invocation.
Framework Overview
This is an async, artifact-driven workflow. Agents do not communicate in real time — they communicate via JSON files in a handoffs/ directory. The flow is:
Planning → Design → Dev (Senior / Junior)
↓ ↓
Documentation ← Security + Tech Review
↓ ↓
Planning (triage) ← findings with severity
All agents must follow the Golden Rules (see CLAUDE.md or run /golden-rules).
Agent Roster
Role skills are namespaced by this plugin (e.g. /agent-based-development:abd-plan). Where your Claude Code resolves unambiguous bare names, the short form also works.
| Agent | Skill | When to Include |
|---|---|---|
| Planning | abd-plan | Almost always — assigns tasks, triages reviews |
| Design | abd-design | When the project has a design phase; omit for simple/script-only work |
| Dev Senior | abd-dev-senior | When there is higher-complexity implementation work |
| Dev Junior | abd-dev-junior | For routine tasks; omit for small teams |
| Security | abd-security | Recommended for all projects |
| Tech Review | abd-review | Recommended for all projects |
| Documentation | abd-docs | Almost always — docs, ToDo, changelogs, assumptions |
| Planning Triage | abd-triage | After reviews land — rework assignments |
| Testing | abd-test | When the project has automated tests |
| DevOps | abd-devops | When the project has CI/CD or a formal release process |
| Status | abd-status | At any time — shows project-wide task and finding status |
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.
- 5d ago First seen · 66 lines · 34 tokens per session scan A b1926a080f73
agent-based-development is a skill published in the GitHub repository RealDougEubanks/ClaudeMarketplace (1 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 965 once invoked, about $0.0002 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 skills, from other repositories
release-notes
Draft a changelog for the next release by summarizing git commits since the last tag. Use only when the user asks to draft release notes, write a changelog entry, or prepare the next version's notes — never trigger automatically.
release-checklist
Generates a comprehensive pre-release validation checklist covering build verification, certification requirements, store metadata, and launch readiness.
changelog
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
start-task
Bootstrap a task into a synced feature branch — one shot, zero confirmations. Detects the source from the args: GitHub issue ('#100', 'issue 100', 'gh issue 100', or bare '100'), Jira key ('PROJ-42'), or a local spec file path; ad-hoc conversation otherwise. Fetches the task, derives {type}/{number}/{slug}, syncs the…
commit
One-shot conventional commit; bundled scripts adaptively gather diff context, draft the message, and stage+commit — pass ask to confirm first or add a hint for the title. Use only when the user asks for a commit.
move-to-worktree
After /start-task: park the current clean, pushed feature branch in its own issue-numbered nested worktree (.worktrees/ ) and return the primary checkout to current main, so the next parallel lane can start. Use when the user says to move the branch or task to a worktree or open a parallel lane.