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/marcusrbrown/dev-like/develop-like-theonpx skills add marcusrbrown/dev-like --skill develop-like-theogit clone --depth 1 https://github.com/marcusrbrown/dev-likeWhat 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.00062 | $0.01030 |
| Opus 5 | $0.00031 | $0.00515 |
| Sonnet 5 | $0.00012 | $0.00206 |
| Haiku 4.5 | $0.00006 | $0.00103 |
Grade A, and why
develop-like-theo 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 2d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Develop like Theo Browne
Profiled as of 2026-07-11 · consent tier: stated · full bibliography in references/sources.md. Cultures drift — if this is more than ~6 months old, re-run
/dev-like theoto refresh.
Core principle
Typesafety absolutism: full-stack TypeScript with a single source of truth and inference over hand-written types; typesafety is a core, non-negotiable axiom [T3 intro] [types & Next.js].
Principles
- Typesafety absolutism — full-stack TypeScript with a single source of truth and inference over hand-written types; typesafety is a core, non-negotiable axiom [T3 intro] [types & Next.js]
- "Bleed responsibly" — reach for bleeding-edge tools only in reversible places where you can afford the cost [T3 intro]
- Build-your-own when unhappy — Ping, UploadThing, T3 Chat all born from dissatisfaction with incumbents [t3dotgg]
- Optimize for delivery + iteration, not architecture cosplay — speed of shipping, DX, and maintainability over ceremony [2023 tech]
- Defaults are opinions — create-t3-app's shipped choices (Next.js, tRPC, Tailwind, Prisma/Drizzle) are his stated best practices, encoded as an executable starter [create.t3.gg] [Drizzle support]
Workflow
Execute these checkpoints before and during the task. Treat them as required actions, not background description:
"Bleed responsibly": reach for bleeding-edge tools only in reversible places where you can afford the cost [T3 intro]. Optimize for delivery and iteration, not architecture cosplay; prioritize speed of shipping, DX, and maintainability over ceremony [2023 tech]. Build your own replacement when unhappy with incumbents — Ping, UploadThing, and T3 Chat were all born that way [t3dotgg]. No further first-party detail on day-to-day process is currently sourced; treat this section as thin and directional rather than a documented methodology.
What ships with it
4 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.
- 2d ago First seen · 74 lines · 62 tokens per session scan A 19070b2b8c95
develop-like-theo is a skill published in the GitHub repository marcusrbrown/dev-like (2 stars, last pushed 2d ago), licensed MIT. It adds 62 tokens to every session and 1,030 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
auth-web-cloudbase
CloudBase Web Authentication Quick Guide for frontend integration after auth-tool has already been checked. Provides concise and practical Web authentication solutions with multiple login methods and complete user management.
fix-codesign-error
Slash command that inspects a macOS signing or entitlement failure and explains the minimum fix path. Invoke explicitly with /fix-codesign-error — this skill never self-triggers.
browse-and-evaluate
Use when exploring the ai-agent-skills catalog to find, compare, and evaluate skills before installing. Always use --fields to limit output size and --dry-run before committing to an install.
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
loop-engineering
Shared loop-engineering reference for COG skills - the agent loop, deterministic verifiers, termination conditions, in-loop context management, and named patterns. Invoke when designing or debugging a skill that iterates (search-verify-retry, scan-until-dry, fetch-retry-gate).
telnyx-messaging-hosted-curl
Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.