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 dburkart/auto-engineer --skill auto-managergit 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/auto-manager)<a href="https://agentmods.dev/skills/dburkart/auto-engineer/auto-manager"><img src="https://agentmods.dev/badge/skills/dburkart/auto-engineer/auto-manager/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/dburkart/auto-engineer/auto-manager"><img src="https://agentmods.dev/badge/skills/dburkart/auto-engineer/auto-manager.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.00110 | $0.03798 |
| Opus 5.5 | $0.00044 | $0.01519 |
| Sonnet 5.5 | $0.00022 | $0.00760 |
| Haiku 4.5 | $0.00011 | $0.00380 |
Grade A, and why
auto-manager 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.
How it starts
The opening of the file, as written. The whole thing — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
auto-manager
Takes either a specific scoping issue or a fuzzy topic, and drives it through to a merged epic without requiring the user to manually file each sub-issue, plan workstreams, or coordinate subagents. The skill owns five phases:
- Discover (fuzzy input only) — explore the open backlog + codebase to gather candidate issues and surface gaps; present a scope proposal for the user to approve before doing anything destructive.
- Scope — read the spec / approved scope, inspect the codebase, file well-scoped sub-issues.
- Refine — iterate with the user on the filed plan (rescope, fold, drop).
- Plan — partition issues into independent workstreams with a dependency graph.
- Orchestrate — spawn
/auto-engineersubagents in parallel (worktree-isolated, background) and respawn as predecessors land.
Read the tracker playbook first: {{PLAYBOOK_TRACKER}}. All tracker operations in this skill — listing the backlog, fetching/editing/commenting/closing issues, filing new ones — go through its recipes. Do not invoke gh issue ... or mcp__github__*_issue directly.
{{#if PLAYBOOK_SDLC}}Then read these shared playbooks:
{{PLAYBOOK_SDLC}}{{PLAYBOOK_PRIORITIZATION}}{{PLAYBOOK_PR_REVIEW}}{{/if}}
Also read the sibling skills you'll call into:
.claude/skills/file-issue/SKILL.md— used in phase 1 for every sub-issue filed..claude/skills/auto-engineer/SKILL.md— hard dependency; phase 4 is meaningless without it.
Hard requirements
/auto-engineermust exist in this project. If not, stop and tell the user.{{PLAYBOOK_TRACKER}}must exist. Without it this skill has no way to read or mutate the backlog.- The repo must have
gh, a code-review gate (CODEOWNERS + reviewers, a review bot, or equivalent), and CI wired up — auto-engineer's loop assumes these. (Note:ghis required for PR/CI operations regardless of tracker; for GitHub-tracker projects it's also used by the tracker playbook's recipes.)
When to invoke
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 · 232 lines · 110 tokens per session scan A ea8001dd0acd
auto-manager is a skill published in the GitHub repository dburkart/auto-engineer (5 stars, last pushed 6mo ago), licensed BSD-3-Clause. It adds 110 tokens to every session and 3,798 once invoked, about $0.0004 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 skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.