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-oxidenpx skills add marcusrbrown/dev-like --skill develop-like-oxidegit 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.00077 | $0.01658 |
| Opus 5 | $0.00039 | $0.00829 |
| Sonnet 5 | $0.00015 | $0.00332 |
| Haiku 4.5 | $0.00008 | $0.00166 |
Grade A, and why
develop-like-oxide 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 yesterday.
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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Develop like Oxide
Profiled as of 2026-07-11 · consent tier: self-published · full bibliography in references/sources.md. Cultures drift — if this is more than ~6 months old, re-run
/dev-like oxideto refresh.
Core principle
Write it down. "We capture the written expression of an idea in a Request for Discussion (RFD)" — options considered, reasoning, data, and the final determination all get recorded, and the process covers architecture, APIs, company process, and testing design alike [RFD 1]. Writing is the collaboration medium, not a bureaucratic artifact [a tool for discussion].
Principles
- Write decisions down — options, reasoning, and determination, in a versioned record [RFD 1]
- Rigor with urgency — thoroughness that ships beats analysis that stalls [RFD 113]
- Name the phase you're in (scoping → … → production) and act accordingly [RFD 5]
- Toolmaking is core engineering work — build the missing tool (buildomat) instead of tolerating friction [sharpening the axe] [buildomat]
- Rust where correctness pays rent, all the way down to firmware [iddqd] [Klabnik]
- Transparency as default — uniform pay, public RFDs, recorded meetings [compensation] [engineering culture]
- Model long-running operations as observable, recoverable workflows — never fire-and-forget [RFD 107]
- Demo working things continuously; trust demos over status reports [engineering culture]
- Keep agent instructions local to the code they govern, and cover every harness in use [omicron PR 10628]
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.
- yesterday First seen · 91 lines · 77 tokens per session scan A 8461766c0d55
develop-like-oxide is a skill published in the GitHub repository marcusrbrown/dev-like (2 stars, last pushed yesterday), licensed MIT. It adds 77 tokens to every session and 1,658 once invoked, about $0.0004 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.