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-devopsgit 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-devops)<a href="https://agentmods.dev/skills/realdougeubanks/claudemarketplace/abd-devops"><img src="https://agentmods.dev/badge/skills/realdougeubanks/claudemarketplace/abd-devops.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.00030 | $0.00461 |
| Opus 5 | $0.00015 | $0.00230 |
| Sonnet 5 | $0.00006 | $0.00092 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
abd-devops 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
ABD — DevOps
Adopt the DevOps 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 the latest plan artifact from
handoffs/plans/. - Use Glob to check for existing CI/CD config files:
.github/workflows/**,bitbucket-pipelines.yml,.gitlab-ci.yml,Dockerfile, anddocker-compose.yml. - If no CI/CD configuration exists, use Write to scaffold a GitHub Actions workflow (
.github/workflows/ci.yml) with jobs for lint, test, and build. - Validate that all required environment variables documented in the plan have corresponding entries in
.env.example; add any that are missing. Never copy real secret values into.env.exampleor workflow files — placeholder values only (e.g.API_KEY=your-api-key-here). - Check Dockerfile hygiene: verify that a non-root user is set, the base image is pinned to a specific digest or version tag, and a
.dockerignorefile is present — report or fix each gap found. - For release tasks, follow the release steps in Git rules: open a PR from the release branch into
mainand tag the release. - Use Write to create a DevOps artifact at
handoffs/dev/{taskId}_devops_{unixTimestamp}.jsonwith status and a summary of all checks performed and changes made.
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.
- 6d ago First seen · 26 lines · 30 tokens per session scan A a768711d8cc4
abd-devops is a skill published in the GitHub repository RealDougEubanks/ClaudeMarketplace (1 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 461 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.
merge-queue-thrash-stop-inflow-and-open-prs-as-drafts
When main moves faster than the slowest CI leg, every open branch goes stale before it can merge and the whole queue jams with nothing red. Use when: (1) several PRs sit at mergeStateStatus BEHIND with auto-merge armed and none of them lands; (2) branches are being updated, re-running CI and going stale again before…
claude-plugin-repo-ci-release
Wire up CI validation and automatic release-cutting for a Claude Code plugin or marketplace repo (a repo with a .claude-plugin/marketplace.json and plugins/). Adds two GitHub Actions — a structure validator that runs on every PR/push, and a release-on-version-bump job that cuts a GitHub Release whenever a VERSION file…
ship
An automated release workflow that commits current changes, pushes them, opens and merges a pull request, and cleans up the branch. A pull request is a proposed code change for review; the workflow adapts to repositories using either a develop branch or direct feature-to-main merging.