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 skills add RealDougEubanks/ClaudeMarketplace --skill abd-dev-seniorgit 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/abd-dev-senior)<a href="https://agentmods.dev/skills/realdougeubanks/claudemarketplace/abd-dev-senior"><img src="https://agentmods.dev/badge/skills/realdougeubanks/claudemarketplace/abd-dev-senior/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/skills/realdougeubanks/claudemarketplace/abd-dev-senior"><img src="https://agentmods.dev/badge/skills/realdougeubanks/claudemarketplace/abd-dev-senior.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.00031 | $0.00301 |
| Opus 5 | $0.00015 | $0.00151 |
| Sonnet 5 | $0.00006 | $0.00060 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
abd-dev-senior 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 10d 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
ABD — Dev Senior
Adopt the Dev Senior role in the Agent-Based Development workflow.
Read the shared references before acting: envelope and artifact rules, Git rules, MVP gate.
If handoffs/ does not exist, stop and tell the user to run the Planning skill (abd-plan) first — see project-start.md.
Instructions:
- Use Read to read plan and design artifacts.
- Implement the assigned work. Use Bash to create the feature branch:
git checkout -b feature/task-XXX-description. Use Edit and Write for implementation. - Verify the MVP gate before marking the task complete.
- Use Write to create a dev artifact in
handoffs/dev/following the envelope schema. - Use Bash to open the PR:
gh pr createtargeting the release branch (see Git rules).
Follow the output format in envelope.md when reporting.
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.
- 10d ago First seen · 24 lines · 31 tokens per session scan A f9f6d7001983
abd-dev-senior is a skill published in the GitHub repository RealDougEubanks/ClaudeMarketplace (1 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 301 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.
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.
finish-worktree
After an issue's PR has squash-merged on GitHub and its issue has closed: fast-forward the default branch, remove the issue-numbered nested worktree (.worktrees/ ), and delete the local feature branch. Use when the user says to finish, tear down, or clean up a lane or worktree for a merged issue.
release-checklist
Generates a comprehensive pre-release validation checklist covering build verification, certification requirements, store metadata, and launch readiness.