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/martian56/claude-engineer/using-claude-engineernpx skills add martian56/claude-engineer --skill using-claude-engineergit clone --depth 1 https://github.com/martian56/claude-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/martian56/claude-engineer/using-claude-engineer)<a href="https://agentmods.dev/skills/martian56/claude-engineer/using-claude-engineer"><img src="https://agentmods.dev/badge/skills/martian56/claude-engineer/using-claude-engineer.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.00058 | $0.00956 |
| Opus 5 | $0.00029 | $0.00478 |
| Sonnet 5 | $0.00012 | $0.00191 |
| Haiku 4.5 | $0.00006 | $0.00096 |
Grade A, and why
using-claude-engineer 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Claude-Engineer
Announce at start: "I'm using claude-engineer to drive this project's lifecycle."
Claude-Engineer is a lifecycle orchestrator for building full greenfield web apps end-to-end. It is opinionated: React or Next.js + Tailwind + a DESIGN.md-driven custom design system on the front, FastAPI + SQLAlchemy 2.0 + Alembic + Pydantic v2 on the back, a polyglot monorepo, Docker for stateful services only, and hard quality gates.
It does NOT reimplement general engineering discipline - it calls into superpowers for that and
adds the whole-project glue superpowers lacks (intake → phased plan → autonomous build → finish, plus
durable cross-session memory).
Iron Laws (violating the letter is violating the spirit)
- Plan-gated. No build work before the user signs off on the phased plan. Heavy alignment up front, then autonomous.
- Greenfield only. Claude-Engineer scaffolds NEW projects on its opinionated stack. It does not onboard existing codebases.
- Customer experience first. Build in this order: DESIGN.md → frontend shells/components → backend APIs → integration.
- Hard quality gates for "done." ALL of: tests + coverage; Playwright E2E with ZERO console errors; WCAG AA; strict types + lint clean. Enforced at the commit gate and at finish.
- Services in Docker, app runs native. Postgres/Redis/MinIO/Mailpit in Docker; frontend & backend run natively in separate shells.
- Trust the ledger.
.claude-engineer/progress.md+memory.md+git logover your own recollection (survives compaction).
The lifecycle and which skill to invoke
| Stage | claude-engineer skill | calls into superpowers |
|---|---|---|
| 0. Conventions/setup | claude-engineer:project-conventions |
- |
| 1. Intake (brief) | claude-engineer:intake-project |
brainstorming |
| 2. Plan (sign-off gate) | claude-engineer:plan-project |
writing-plans |
| 3. Memory init | claude-engineer:project-memory |
- |
| 4. Build (autonomous) | claude-engineer:execute-build |
using-git-worktrees, subagent-driven-development (each task: test-driven-development), dispatching-parallel-agents, executing-plans (fallback), systematic-debugging |
| - design system | claude-engineer:design-system |
- |
| - frontend | claude-engineer:frontend-development |
- |
| - backend | claude-engineer:backend-development |
- |
| - monorepo/tooling | claude-engineer:monorepo-and-tooling |
- |
| - local services | claude-engineer:docker-dev-environment |
- |
| 5. Verify/review | claude-engineer:testing-and-quality |
requesting-code-review, receiving-code-review, verification-before-completion |
| 6. CI + finish | claude-engineer:ci-cd-pipeline, then finishing-a-development-branch |
finishing-a-development-branch |
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 · 52 lines · 58 tokens per session scan A b03da6b6c303
using-claude-engineer is a skill published in the GitHub repository martian56/claude-engineer (2 stars, last pushed 2mo ago), licensed MIT. It adds 58 tokens to every session and 956 once invoked, about $0.0003 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
adopt-project
Apply agent-starter patterns to an EXISTING project - audits the codebase, proposes components by invasiveness tier (hooks, skills, CLAUDE.md, lint configs, patterns), and applies only what the developer approves. Use when the user says adopt, retrofit, "apply agent-starter to this project", or wants starter patterns…
commit-push-pr
Full git workflow - creates branch, commits, pushes, and creates or updates a PR with summary and test plan.
commit
Create a single well-crafted git commit from current changes. Analyzes diff, follows repo's commit style, and writes a concise "why not what" message.
remember
Review auto-memory entries and propose promotions to CLAUDE.md, CLAUDE.local.md, or shared memory. Also detects outdated, conflicting, and duplicate entries across memory layers.
reflect
Per-project self-improvement - reads the .harness ledger and feedback memories, then proposes gated rule/threshold/ADR changes so the project stops repeating mistakes. Run periodically.
dream
Memory consolidation - review, merge, prune, and index memory files. Run periodically to keep memories organized and up-to-date.