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-everynpx skills add marcusrbrown/dev-like --skill develop-like-everygit 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.00070 | $0.01022 |
| Opus 5 | $0.00035 | $0.00511 |
| Sonnet 5 | $0.00014 | $0.00204 |
| Haiku 4.5 | $0.00007 | $0.00102 |
Grade A, and why
develop-like-every 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Develop like Every
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 everyto refresh.
Core principle
"Each unit of engineering work should make subsequent units easier — not harder" [CEP README]. Roughly 80% of effort goes to planning and review, 20% to execution [guide].
Principles
- Plan-first, 80/20 — most effort before code [guide]
- Compound every unit of work into reusable repo knowledge [CEP]
- Simplify as an explicit pipeline step, not an afterthought [CEP]
- One person + agents ≈ a team; design workflows for that ratio [podcast transcript]
- Boring stack, radical process [SF Ruby keynote]
- Agent-native parity — if a human can run tests, read logs, or open a PR, the agent should be able to as well [guide]
- Safety nets over gatekeeping — trust comes from tests, automated review, monitoring, and rollback, not line-by-line babysitting [guide]
- Make institutional knowledge discoverable — solved problems live in
docs/solutions/, and instruction files must surface that store so future agents find it [ce-compound-refresh]
Workflow
Execute these checkpoints before and during the task. Treat them as required actions, not background description:
Run the six-step loop: brainstorm → plan → work → simplify → review → compound
[CEP]. Use the four-beat core cycle
— plan → work → review → compound → repeat — and keep simplify as the extra gate the
plugin inserts [guide]. At the compound step
(/ce-compound), write learnings to docs/solutions/ and use them to ground the next loop —
make knowledge accrete in the repo, not in heads
[ce-compound].
For the fully autonomous pipeline (/lfg), plan → work → review → PR → watch CI until green.
Keep reviewer personas as skill-local prompt assets (29 skills, 0 standalone agents post-migration)
[CEP].
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 · 65 lines · 70 tokens per session scan A b6f65239526e
develop-like-every is a skill published in the GitHub repository marcusrbrown/dev-like (2 stars, last pushed yesterday), licensed MIT. It adds 70 tokens to every session and 1,022 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.