Borrowing it
Nothing to install: this file belongs to jpeseWang/solo-dev-workflow. 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/jpeseWang/solo-dev-workflow/main/AGENTS.mdgit clone --depth 1 https://github.com/jpeseWang/solo-dev-workflowWrote 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/instructions/jpesewang/solo-dev-workflow/agents-md)<a href="https://agentmods.dev/instructions/jpesewang/solo-dev-workflow/agents-md"><img src="https://agentmods.dev/badge/instructions/jpesewang/solo-dev-workflow/agents-md/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/instructions/jpesewang/solo-dev-workflow/agents-md"><img src="https://agentmods.dev/badge/instructions/jpesewang/solo-dev-workflow/agents-md.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.02242 | $0.02242 |
| Opus 5.5 | $0.00897 | $0.00897 |
| Sonnet 5.5 | $0.00448 | $0.00448 |
| Haiku 4.5 | $0.00224 | $0.00224 |
Grade A, and why
solo-dev-workflow AGENTS.md 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 2mo 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solo Dev Workflow — Agent Guide
Portable working agreement for an AI coding assistant pairing with a solo developer. This file is the universal source of truth. It is read automatically by Antigravity, Cursor, Codex, Zed and other
AGENTS.md-aware tools, and is wired into Claude Code (CLAUDE.md) and GitHub Copilot (.github/copilot-instructions.md) byinstall.sh.
You are pairing with one developer who owns the whole codebase — there is no team to review, no ticket system, no manager. Optimize for shipping correct code fast with a lightweight, durable trail (git history + two local files). Do not add ceremony that only makes sense for teams (worklog accounting, review-count metrics, approval gates).
The workflow
idea ──▶ /plan ──▶ code ──▶ /review ──▶ /test ──▶ /commit ──▶ /ship ──▶ /wrap
│ ▲ │
│ └────────── iterate while coding ─────────┘
▼ ▼
TASKS.md (active) TASKS.md (done) + CHANGELOG.md
/setup — once, right after installing
/debug — any time something is broken, then rejoin at /review
/verify — run it and look at it; tests passing is not the feature working
| Command | When | What it does |
|---|---|---|
/setup |
Once, after installing | Detect the stack and fill in Project context below |
/plan |
Starting anything non-trivial | Clarify scope, write a short checklist, add a TASKS.md entry, create a branch |
/debug |
Something is broken | Reproduce, isolate, fix the root cause, leave a regression test |
/review |
Before committing | Self-review the uncommitted diff from 3 angles. Concrete findings, no auto-fix unless asked |
/test |
Before/after a change | Generate or strengthen tests for the changed code, then run them |
/verify |
Change should visibly work | Run the app, exercise the real path, report what was observed |
/commit |
Change is ready | Quality-gate the diff (4 dimensions), auto-fix safe issues, write a Conventional Commit |
/ship |
Branch is done | Push and open a GitHub PR via gh (title + body from commits). Optionally merge |
/wrap |
Task finished | Mark the TASKS.md entry done, append a CHANGELOG.md line, summarize what shipped |
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.
- 2mo ago First seen · 178 lines · 2,242 tokens per session scan A b81e43dae3b1
solo-dev-workflow AGENTS.md is an instructions file published in the GitHub repository jpeseWang/solo-dev-workflow (2 stars, last pushed 2mo ago), licensed MIT. It adds 2,242 tokens to every session, about $0.0090 per session on Opus 5.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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.