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/commit)<a href="https://agentmods.dev/rules/first-fluke/fullstack-starter/commit"><img src="https://agentmods.dev/badge/rules/first-fluke/fullstack-starter/commit/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/commit"><img src="https://agentmods.dev/badge/rules/first-fluke/fullstack-starter/commit.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.00010 | $0.00264 |
| Opus 5.5 | $0.00004 | $0.00106 |
| Sonnet 5.5 | $0.00002 | $0.00053 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
commit 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- commit — 86% identical, 3 lines differ
What it actually says
Commit Standards
Format
<type>(<scope>): <description>
[optional body]
Types: feat, fix, refactor, docs, test, chore, style, perf, build, ci, revert
Rules
- Analyze changes before committing
- Split by feature if changes span multiple domains
- Description under 72 characters, imperative mood, lowercase, no trailing period
- Never use
git add -Aorgit add .without explicit permission - Never commit files that may contain secrets (.env, credentials)
- Always use specific file names when staging
- Split commits when: different scopes, different types, logically independent changes
- Do NOT split when: all changes belong to a single feature, few files (5 or fewer)
- Precedence: logical independence decides first (one logical change = one commit); file count (5 or fewer) is only a tiebreaker; an explicit user instruction overrides both
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.
- 1mo ago First seen · 32 lines · 10 tokens per session scan A 3513b00455e7
commit is a cursor rule published in the GitHub repository first-fluke/fullstack-starter (224 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 264 once invoked, about $0.0000 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
project-core
Repository-wide project instructions. Canonical rules are in AGENTS.md.
git-flow
Branching, commits and PR hygiene. Always applies.
git
Git commit, branch, and PR conventions for this repository.
version-management
Automatically commit and push changes after completing any feature, bug fix, or significant addition.
git-consent
Git — consent for commits/push; amend; context before risky git ops.
atualizar-readme
Atualizar README ao subir commit, se a mudanca exigir.