development-workflow

A rule document about the development workflow for Bordful, a job-board starter kit built with Next.js and Airtable.

In plain words
What is it for?
Development work in the Bordful project.
Why use it?
It may guide how development work is carried out, but no specific workflow rules were provided.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/craftled/bordful/development-workflow
Clone the repo
git clone --depth 1 https://github.com/craftled/bordful

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 12 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00012
Opus 5 $0.00000 $0.00006
Sonnet 5 $0.00000 $0.00002
Haiku 4.5 $0.00000 $0.00001

Measured 2d ago against content hash bc6746a8a253, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

development-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 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.

Origin

This is a copy

100% identical to code-commenting-standards — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.cursor/rules/development-workflow.mdc · 6 lines

The source is not reproduced here

Licensed MIT

The repository is licensed MIT, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

Changes

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.

  1. 2d ago First seen · 6 lines · 0 tokens per session scan A bc6746a8a253

Subscribe to this mod's changes

development-workflow is a cursor rule published in the GitHub repository craftled/bordful (68 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 12 tokens. A static security scan graded it A with 0 findings. It is 100% identical to code-commenting-standards, differing in 2 lines, and is treated as a copy.