Borrowing it
Nothing to install: this file belongs to lucasgodt/open-agent-ready-typescript. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lucasgodt/open-agent-ready-typescript/main/.claude/skills/scaffold-agent-ready/SKILL.mdgit clone --depth 1 https://github.com/lucasgodt/open-agent-ready-typescriptWrote 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/lucasgodt/open-agent-ready-typescript/scaffold-agent-ready)<a href="https://agentmods.dev/skills/lucasgodt/open-agent-ready-typescript/scaffold-agent-ready"><img src="https://agentmods.dev/badge/skills/lucasgodt/open-agent-ready-typescript/scaffold-agent-ready/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/lucasgodt/open-agent-ready-typescript/scaffold-agent-ready"><img src="https://agentmods.dev/badge/skills/lucasgodt/open-agent-ready-typescript/scaffold-agent-ready.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.00145 | $0.01160 |
| Opus 5 | $0.00072 | $0.00580 |
| Sonnet 5 | $0.00029 | $0.00232 |
| Haiku 4.5 | $0.00015 | $0.00116 |
Grade A, and why
scaffold-agent-ready 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scaffold Agent-Ready TypeScript Project
Creates a new TypeScript project that inherits the five machine-enforced guardrails from https://github.com/lucasgodt/open-agent-ready-typescript, adapted to the user's domain and project shape. You are not copying an example app — you are transplanting a guardrail system and growing a new domain inside it.
The five guardrails (every variant, non-negotiable)
- Dependency rule as a build gate — dependency-cruiser config wired into
verify, the commit hook and CI. The domain layer/package imports nothing. - Mutation testing (Stryker) on domain + application code, break < 75%.
- Protected tests and specs — the PreToolUse hook blocks agent edits to
tests/**andspecs/**without a human-created.agent/allow-test-edits. - Commit gate — a hook runs the full verify suite on
git commit, blocking on failure and feeding errors back to the agent. - Spec-driven development as a build gate — one Given/When/Then spec
per use case, tests mirroring criteria one
it("N. ...")per criterion, enforced byscripts/check-spec-coverage.mjsinsideverify(use case without spec, orphan spec, or unmirrored criterion all fail the build).npm run new -- <name>scaffolds the golden path. Hierarchical AGENTS.md.
Step 0 — Gather what you need
Ask the user (only what's missing from context):
- Project name and target directory.
- Shape: backend API/service, frontend app, or monorepo? If they describe "an app with an API and a web client", that's a monorepo.
- Domain: what the software does, in one sentence, plus the 2–5 core operations (these become the first use cases).
- Anything to skip.
Step 1 — Read the variant reference
Read exactly one file before scaffolding, and follow it:
- Backend API/service →
references/backend.md - Frontend app (React/Vite) →
references/frontend.md - Monorepo (apps + packages) →
references/monorepo.md
Do not blend variants from memory; the monorepo reference already composes the other two where relevant.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 86 lines · 145 tokens per session scan A 652fd6e3887b
scaffold-agent-ready is a skill published in the GitHub repository lucasgodt/open-agent-ready-typescript (5 stars, last pushed 1mo ago), licensed MIT. It adds 145 tokens to every session and 1,160 once invoked, about $0.0007 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
lang-typescript
TypeScript toolchain: ESLint, tsc, Jest/Vitest, npm. CI gate commands, file layout, type standards, Node 20. Use when working on a TypeScript or JavaScript project.
migrate-to-shoehorn
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
V3 Core Implementation
Core module implementation for claude-flow v3. Implements DDD domains, clean architecture patterns, dependency injection, and modular TypeScript codebase with comprehensive testing.
migrate-to-shoehorn
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
typescript-test-writing
Use this skill when writing or modifying tests in the llxprt-code repository. Covers mandatory TDD, behavioral testing, bun:test conventions and file naming, mock hygiene (no mock theater), and what never to test. Distilled from dev-docs/RULES.md, which remains the source of truth.
typescript
TypeScript strict mode with eslint and jest.