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.
git clone --depth 1 https://github.com/first-fluke/fullstack-starterWrote 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/rules/first-fluke/fullstack-starter/dev-workflow)<a href="https://agentmods.dev/rules/first-fluke/fullstack-starter/dev-workflow"><img src="https://agentmods.dev/badge/rules/first-fluke/fullstack-starter/dev-workflow/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/rules/first-fluke/fullstack-starter/dev-workflow"><img src="https://agentmods.dev/badge/rules/first-fluke/fullstack-starter/dev-workflow.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.00018 | $0.00231 |
| Opus 5.5 | $0.00007 | $0.00092 |
| Sonnet 5.5 | $0.00004 | $0.00046 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
dev-workflow 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 today.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- dev-workflow — 100% identical, 4 lines differ
What it actually says
Developer Workflow Standards
Core Rules
- Use
mise runtasks instead of direct package manager commands - Run
mise installafter pulling changes that update runtime versions - Use parallel tasks for independent operations. Cap concurrency when more workers slow the same suite
- Run lint and test on changed scope. Keep a selector that fails closed on shared or unknown paths
- Validate commit messages with commitlint before committing
- Configure CI to skip unchanged apps for faster builds
- Check
mise tasks --allto discover available tasks before running - Pin runtime versions in mise.toml for consistency
- Never use direct package manager commands when mise tasks exist
- Never modify mise.toml without understanding task dependencies
- Never hardcode secrets in mise.toml files
- Never skip reading task definitions before running unfamiliar tasks
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.
- today Changed 29057a437340
- 1mo ago First seen · 25 lines · 18 tokens per session scan A aea01dfad5e7
dev-workflow is a cursor rule published in the GitHub repository first-fluke/fullstack-starter (224 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 231 once invoked, about $0.0001 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-09-03.
Other cursor rules, from other repositories
no-mvn-compile
Do not run mvn compile; rely on IDE lint errors.
terradart
TerraDart shared project guide.
desktop-release-gate
Desktop app fixes must pass a local packaged build smoke test before pushing release tags or CI desktop builds.
ci-cd-workflows
This rule provides guidance on the CI/CD pipeline, GitHub Actions workflows (defined in .github/workflows/), custom actions (in .github/actions/), versioning strategies, and release processes. Use this rule if the query involves CI/CD, build/test issues, release procedures, versioning questions, or if it references…
dev-workflow
Monorepo developer workflow standards - mise tasks, git hooks, CI/CD, release automation.
sciclaw-papercuts
Papercuts from Sol/ImageMagick/release cycles — release, brew, CI, and workspace hygiene for sciClaw agents.