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/dburkart/auto-engineer/sdlcnpx skills add dburkart/auto-engineer --skill sdlcgit clone --depth 1 https://github.com/dburkart/auto-engineerWrote 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/dburkart/auto-engineer/sdlc)<a href="https://agentmods.dev/skills/dburkart/auto-engineer/sdlc"><img src="https://agentmods.dev/badge/skills/dburkart/auto-engineer/sdlc.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 | $0.00037 | $0.00968 |
| Opus 5 | $0.00018 | $0.00484 |
| Sonnet 5 | $0.00007 | $0.00194 |
| Haiku 4.5 | $0.00004 | $0.00097 |
Grade B, and why
sdlc scanned grade B with 1 finding 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 4d 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
Before editing any skill file, confirm it lives under `templates/skills/`. If you find yourself reaching for `.claude/skills/`, stop and re-read the issue — you almost certainly have the wrong file. How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDLC
Read docs/agent-playbooks/sdlc.md first for repo-level branch, commit, push, and PR policy.
Read docs/agent-playbooks/pr-review.md when the task includes CI interpretation or review response.
When to use this skill
Use this skill when the task involves:
- starting a new cohesive change on its own branch
- deciding what checks to run before push
- preparing a PR body and opening a PR
- responding to review feedback without rewriting reviewed history
Branch naming
Create a branch per unit of work. Conventional patterns:
m<issue-number>-<slug>for issue-tracked work<verb>-<noun>for untracked changes (e.g.fix-login-timeout,add-metrics-endpoint)
Always branch from an up-to-date main:
git checkout main && git pull
git checkout -b <branch>
Commits
- Group related changes into coherent commits — not one mega-commit, not micro-commits per line.
- Use the imperative mood in the subject line (
Add,Fix,Remove, notAdded,Fixed). - Each commit must include the trailer:
Co-Authored-By: Claude Opus 4.6 <[email protected]> - Never commit directly to
main.
Opening a PR
Use the standard Summary + Test plan body structure:
## Summary
- <bullet describing what changed and why>
## Test plan
- [ ] <concrete test step>
- [ ] <edge case to verify>
Closes #<N>
Open via mcp__github__create_pull_request. No "generated with Claude" footer.
CI and review follow-up
- If CI or review follow-up is needed, hand off to
wait-for-prfor Claude-specific polling and automation. - Review classification still comes from
docs/agent-playbooks/pr-review.md.
Self-review (required for this project)
This project has no review bots or CI tests, so every PR must get an independent review before merge. Before requesting merge:
- Spawn a review subagent via the
Agenttool with a prompt framing it as a Senior prompt engineer reviewing the diff for correctness, security, performance, and adherence to project conventions. - Pass the agent the PR number and the full diff (
gh pr diff <N>); instruct it to report blocking issues, in-scope nits, and out-of-scope suggestions separately, and to keep its reply under 400 words. - Triage its findings using the same actionable/nit/out-of-scope classification above. Address blockers in a new commit on the branch; file follow-up issues for deferred items.
- Record in the PR body (under "Test plan") that a self-review was performed and link the resulting commits or issues.
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.
- 4d ago First seen · 98 lines · 37 tokens per session scan B d1ae7c6913ca
sdlc is a skill published in the GitHub repository dburkart/auto-engineer (5 stars, last pushed 4mo ago), licensed BSD-3-Clause. It adds 37 tokens to every session and 968 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
apm-issue-autopilot
Use this skill to drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR with triage as the central, paramount gate. Run the apm-triage-panel rubric per issue first, then present ONE consolidated triage review for the whole batch and escalate to the maintainer BY…
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
omh-ralph-task
Execute one omh-ralph task: file-scope, commit, report.
worklog
Issue-led atomic work logging. Use whenever the user says "worklog" or asks to run, apply, start, maintain, update, summarize, or close a worklog; also use for issue-led development, master or umbrella issue tracking, one-issue-per-bug/feature/change workflows, atomic issue-scoped commits, GitHub issue comment…
smith-build
Autonomous build phase — generates tasks, implements, tests, commits, pushes, merges, and produces release notes. Runs without user interaction.
abo-issue-create
Create or reuse GitHub issues for Audiobook Organizer work, then prepare the correct issue branch from master. Use before non-trivial code or documentation edits in this repository.